| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Task-number: QTBUG-95173
Change-Id: I541dc26cf2cdd6f2640824f693f7d059445367d9
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Delivery order has changed to be the same as the z-axis stacking order
(since qtdeclarative 3ff11ceca37dcc4b6f0420332fa7f6aa007be7f3).
Since QQuickSwipeDelegate puts its children under itself by setting
negative z-values, it can now receive mouse events before those
negative-z children, directly rather than via childMouseEventFilter().
It doesn't seem to be enough to ignore() the events and let them
propagate: we now need to explicitly forward them to interactive
child items, and to child items' Attached objects, if any.
Pick-to: 6.0 6.1
Fixes: QTBUG-87018
Fixes: QTBUG-87789
Change-Id: I1e02ceddad7c3221fb09a33046941d654bfa8a4b
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
|
|
|
|
|
|
|
|
|
| |
This has a long history of being flaky. Until we decide what to do with
it, blacklist it to unblock CI.
Task-number: QTBUG-70597
Change-Id: Ic115a345662fc61464065d678720c88597181d98
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
|
|
|
|
|
|
|
|
| |
This passes for me locally on both macOS and Linux.
Task-number: QTBUG-87018
Change-Id: I2d5f27f3f18e8c419485beb1714515b86723bb08
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
|
|
|
|
|
|
|
|
|
| |
cd669f1f216e54fa59eee77459d608a41f5df290 fixed these tests,
but I forgot to unblacklist them in that patch.
Task-number: QTBUG-87018
Change-Id: I50b4f571eb9b231449e320ad90da3a9d4ae59a88
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
So that we can unblock CI.
The failures need more time to be looked into.
Task-number: QTBUG-87018
Change-Id: I350a4100011127588077edecb73ae11078100940
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After 1f4bfc099b7e48e2cc3dd9488b7b42a96122b299 in qtdeclarative,
QQuickWindow does not cause the Item to which it's about to attempt
to deliver an event to pre-grab. (That caused a lot of thrashing
of the grabber, so not doing that is a nice simplification, and
also avoids the need to ungrab later, and also makes mouse event
handling more like touch event handling.) So whenever SwipeDelegate
knows at the time of mouse press that it wants to see the release
too, it should grab. The grabber can be either the Item for which
it's filtering events, or the SwipeDelegate itself, whichever is
more appropriate in any given scenario. For now I assume it should
be the delivery-target Item, because that's what would have had the
grab before.
Task-number: QTBUG-62412
Task-number: QTBUG-62631
Change-Id: Ie01276508c6602b10f9d7996a748ffe90efa36b5
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Running this test causes tests after it to fail, mainly those related
to hover. Since we need to fix the root cause of the recent failures
before the release, it shouldn’t matter too much that this test isn’t
run for a bit.
Task-number: QTBUG-62549
Change-Id: Id8fd00e9049890ae47504c3e4b4ea3dda8ac60ef
Reviewed-by: Jani Heikkinen <jani.heikkinen@qt.io>
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This test started failing after the recent wip/pointerhandler to dev
merge in declarative. Until a fix can be found, we'll blacklist the
test so that integration isn't blocked.
The issue will need to be fixed before the release.
Task-number: QTBUG-62549
Change-Id: Ib72c39ca74c69cf33bd995f9572bf4a9a5b2f680
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
|
|
Some tests started failing after the recent wip/pointerhandler to dev
merge in declarative. Until a fix can be found, we'll blacklist the
tests so that integration isn't blocked.
The issues will need to be fixed before the release.
Task-number: QTBUG-62412
Change-Id: Idfa887f979c946311136a4ee1438ee2921267214
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
|