Details
-
Bug
-
Resolution: Out of scope
-
P2: Important
-
None
-
6.5.3, 6.6.3, 6.7.0
-
Windows Surface tablet; Windows 10 Pro 22H2
Description
Windows Surface tablet has its own virtual keyboard. There is a keyboard icon in the System Tray to explicitly show/hide it, but it also appears on its own implicitly when you tap in a text field on any app.
See attached QML Main.qml which contains 3 fields. All areĀ TextInput but only the 2nd field has echoMode: TextInput.Password.
Reproduce the problem
- Start Google Chrome. (See my notes below for an explanation why.)
- Run the QML project from Qt Creator.
- Manually show then hide the virtual keyboard (from System Tray).
- Switch to Google Chrome and tap in the address field. This triggers the virtual keyboard to appear without you explicitly requesting it.
- Now go to the QML app and tap in the first field. The virtual keyboard will have disappeared while you were navigating apps but will now appear.
- The input fields are connected with Tab navigation. So either type in each field and tab to the next one or tap in each field to select it. Whenever the 2nd field has active focus you'll notice the virtual keyboard disappears.
Important notes
- If you were to manually show the virtual keyboard from System Tray, it would remain throughout and the bug would not be triggered... so it's something to do with implicitly showing it.
- If you change the 2nd field to `echoMode: TextInput.PasswordEchoOnEdit`, the problem doesn't show itself... so it's specific to `TextInput.Password`.
- Qt Creator 12.0.1 suffers this problem in its editors too. If you tap in an editor window, the virtual keyboard appears momentarily and then disappears. (I haven't logged a separate bug for this, but you might want to.)
- If you don't do the step of switching to Google Chrome, it is hit and miss as to whether the virtual keyboard will appear when you tap into any of the `TextInput` fields. Sometimes it appears immediately, sometimes you tap a couple of times and it appears, sometimes it never appears. But somehow by going to a 'robust' app like Google Chrome and triggering the virtual keyboard to appear there, it then means it will show up reliably in the QML app.
I have also attached a video of this problem happening in the field, as reported by one of my users. (Note that my app is full-screen meaning the System Tray is not visible so users cannot easily show/hide the keyboard from there.)
Attachments
Issue Links
- relates to
-
QTBUG-100223 Touchscreen: Discrepancy between QML TextInput and QLineEdit behaviour with Windows virtual keyboard
- Closed