Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
6.7.0 RC2
-
None
-
Windows 10 22H1 (Microsoft Surface Pro 2) + Firefox 124; Android 14 (Google Pixel 7) + Firefox 124
Description
Not sure if this issue lies in Firefox or Qt, but either way it makes Qt for WASM quite unusable
Code
import QtQuick import QtQuick.Controls.Basic Window { width: 640 height: 480 visible: true Column { TextField {} TextInput {} Button { text: "Click me to remove keyboard focus" } } }
Steps to reproduce
- Run the code above using Qt for WASM single-threaded, on a device with a touchscreen (without setting QT_IM_MODULE)
- Tap the TextField
Expected outcomes
When the TextField is tapped, its border lights up and the native virtual keyboard appears. We can use the native virtual keyboard to input text.
Expected outcomes were seen on the following (all with touchscreens):
- Chrome on Windows 10 22H1
- Edge on Windows 10 22H1
- Edge on Android 14
- Firefox on iOS 16
- Safari on iOS 16
Actual outcomes (Firefox on Windows with touchscreen + Firefox on Android)
When the TextField is tapped, its border lights up (expected). However, the native virtual keyboard does NOT appear (not expected).
Some interesting behaviour observed on Firefox on Android 14 (does not apply to Firefox on Windows):
- If I double-tap the TextField, the native virtual keyboard appears for a brief moment and then disappears.
- If I double-tap-and-hold the TextField, the native virtual keyboard remains open and can be used to input text.
- I get similar results with TextInput instead of TextField – however, they are triggered by single-tap instead of double-tap