aboutsummaryrefslogtreecommitdiffstats
path: root/tests
diff options
context:
space:
mode:
authorShawn Rutledge <shawn.rutledge@qt.io>2020-11-13 23:04:39 +0100
committerShawn Rutledge <shawn.rutledge@qt.io>2020-11-17 13:32:25 +0000
commit0506fba1a862a30af5dcd9c5e240a8fb2fe304cf (patch)
tree3b6d11390ed10f21759e9108fbc4b87d49b8c847 /tests
parent3073a81e90c8d835dfccccf8b3a080a93ed0d2af (diff)
When Flickable filters UngrabMouse, react as if it was ungrabbed itself
Fixes tst_QQuickListView::touchCancel again. In this scenario, a TouchCancel is sent, but gets turned into an UngrabMouse for delivery to the MouseArea which is the current grabber. We try to avoid calling QQuickWindow::mouseGrabberItem() because it's too vague a question to ask (which mouse? or did you mean the synth-mouse during synthesis from a touch or tablet event?); and now it acts different anyway, because eventsInDelivery.top() is an UngrabMouse, which did not include a pointer to the QPointingDevice until now. So now we turn the UngrabMouse event into a QSinglePointEvent so that it's possible to get exclusiveGrabber() and check that the grabber is not the same Flickable. (Otherwise, the grabber that's getting ungrabbed is usually the child receiver item sent to childMouseEventFilter().) Task-number: QTBUG-86729 Task-number: QTBUG-74679 Change-Id: I6dfd96686bdfb54723bbe093406b6ab1f75de855 Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
Diffstat (limited to 'tests')
-rw-r--r--tests/auto/quick/qquicklistview/BLACKLIST2
1 files changed, 0 insertions, 2 deletions
diff --git a/tests/auto/quick/qquicklistview/BLACKLIST b/tests/auto/quick/qquicklistview/BLACKLIST
index 414f21b347..1984999130 100644
--- a/tests/auto/quick/qquicklistview/BLACKLIST
+++ b/tests/auto/quick/qquicklistview/BLACKLIST
@@ -12,7 +12,5 @@ macos
macos
opensuse-leap
ubuntu-18.04
-[touchCancel]
-* # QTBUG-86729
[sectionsSnap]
macos ci # QTBUG-86729