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

Android: cursor movement in TextEdit is not tracked, so it can go behind the soft-keyboard

    XMLWordPrintable

Details

    • Android
    • 5c6b10c3cee5737dbc041d0463220898c8120807 (qt/qtbase/dev) 9a81a9766c56f4a99172b105d892c905278065a4 (qt/tqtc-qtbase/tqtc/lts-5.15)

    Description

      When editing text with many lines it can happen that the cursor goes behind the software keyboard. See qtbug-91073.mp4.

      Attachments

        1. qtbug-91073.mp4
          347 kB
          Piotr Mikolajczyk
        2. qtbug91073.zip
          2 kB
          Piotr Mikolajczyk

        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
          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
          resulted in

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-97503 Reg[5.15.2-5.15.6] Android: Keyboard covers the inputfield

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Activity

            People

              piotrmi Piotr Mikolajczyk
              piotrmi Piotr Mikolajczyk
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: