Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-91035

When TextEdit's cursor goes out of bounds of a parent Flickable, the Flickable does not adjust its content coordinates.

    XMLWordPrintable

Details

    • Android, Linux/X11

    Description

      Cursor in edit field is not tracked in any way by Flickable  This is causing it to hide any cursor that is in a TextEdit/TextArea as it is not possible to automatically adjust as a result. See cursor out of screen X11.mp4

      The example attached has the solution in place to move the Flickable up when needed to show the cursor. To reproduce click inside TextArea editable 8 and then press enter and the cursor will end up out of the screen.

      As potential solution would be adding a new property to TextEdit that would point onto Flickable, the TextEdit resides in. So, the Flickable would have its content coordinates updated to show the cursor on the screen.

      Attachments

        Issue Links

          is required for

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-81937 The area used by the keyboard is incorrectly reported when a Flickable is in place

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-62529 [Android]: When a TextEdit is in between two items then clicking on the TextEdit will cause the application to resize when showing the keyboard which means it does not place the cursor correctly

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed
          resulted from

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-62529 [Android]: When a TextEdit is in between two items then clicking on the TextEdit will cause the application to resize when showing the keyboard which means it does not place the cursor correctly

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-81937 The area used by the keyboard is incorrectly reported when a Flickable is in place

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              qtandroidteam Qt Android Team
              piotrmi Piotr Mikolajczyk
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:

                Gerrit Reviews

                  There are no open Gerrit changes