Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
6.7.0
-
None
-
-
2ed64adb9 (dev)
-
2023wk50FOQtforAndroid, 2023wk52FOQtforAndroid, 2024wk04FOQtforAndroid, 2024wk10FOQtforAndroid, 2024wk16FOQtforAndroid
Description
Running the test case tst_QGraphicsProxyWidget::focusProxy_QTBUG_51856() on Android leads to many calls to show the software keyboard, which in Android QPA plugin is done by posting a Runnable to handle it on the Android main event queue, with a 15 ms delay. Since this is done on the Activity level, when the view and window leading to the call are destroyed, those Runnables are not cleared up from the event queue, leading to the keyboard being shown during subsequent, unrelated test cases, causing random failures.
Those calls should be cleared away when the view/window they originate from is destroyed. Could also be worthwhile to not make the call a new every time.
Attachments
Issue Links
- relates to
-
QTBUG-118139 Fix keyboard input not working for child windows
-
- Closed
-
Gerrit Reviews
For Gerrit Dashboard: QTBUG-119574 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
522319,4 | Android: Skip focusProxy_QTBUG_51856() test case temporarily | dev | qt/qtbase | Status: MERGED | +2 | 0 |