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

Keyboard does not get focus on Android TV

    XMLWordPrintable

Details

    • Android, Other
    • 2971dbfe0 (dev), b60db83fa (6.8), d97bfafa8 (dev), 229cff37c (dev), 34d184911 (dev), 4de9b9404 (dev), 0cb75c28a (6.8), e27e9d4a2 (6.8), 7e4b10677 (6.8), 0a32e20b1 (6.8)
    • 2024wk42s3FOQtforAndroid, 2024wk44s3FOQtforAndroid, 2024wk46s3FOQtforAndroid, 2024wk48s3FOQtforAndroid

    Description

      After the fix for QTBUG-124360 - the Keyboard is opening by default when focus is set on TextField. The problem is now different:
      "The Keyboard does not get focus and cannot be controlled by remote control".

      I compared the current dev version and with 6.6.3.

      It looks like this:

      • DEV -> keyboard opens - but can't type anything (not focused?)
      • 6.6.3 -> keyboard opens and can type normally

      Recording below:

      QTBUG-130000_REPRO.mp4

       

      Keyboard should be controlled by remote control on TV

      Attachments

        1. QTBUG-124360-Qt663-3.mp4
          1.81 MB
        2. QTBUG-124360-Qt681-3.mp4
          1.20 MB
        3. QTBUG-130000_REPRO.mp4
          3.29 MB

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-125854 [REG: 5->6] android: Virtual keyboard immediately reappears if accepted

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

          User Story - Created by Jira Software - do not edit or delete. Issue type for a user story. QTBUG-98984 Android 11 - IME transitions

          • P3: Somewhat important - Should be fixed, but doesn't affect the release in any way.
          • Open
          split from

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-124360 Android TV system keyboard no long opens on text fields in 6.7

          • 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
          mentioned in

          Page Loading...

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              bartlomiejmoskal Bartlomiej Moskal
              bartlomiejmoskal Bartlomiej Moskal
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: