Details
-
Type:
Bug
-
Status: Closed
-
Priority:
P1: Critical
-
Resolution: Done
-
Affects Version/s: 5.11
-
Fix Version/s: 5.11.0 Beta 3
-
Component/s: Location
-
Labels:None
-
Environment:Ubuntu 17.04
-
Commits:5af3f07c95e758636090ad4a928fa8e86a7b2dc6
Description
In declarative_ui::MouseArea tests if the mouse press is on mouseOverlapper and mouseLower MouseAreas and then release is on mouseOverlapper and mouseUpper, then the next mouseClick() on mouseUpper does not work.
A test function to demonstrate:
function test__release_does_not_block_clicked() { clear_data() mousePress(map, 55, 75) compare(mouseOverlapperPressedSpy.count, 1) mouseRelease(map, 55, 25) // This should follow the same logic as Flickable compare(mouseOverlapperReleasedSpy.count, 0) mouseClick(map, 25, 25) // The following fails: compare(mouseUpperClickedSpy.count, 1) }
This effect caused failures described in https://bugreports.qt.io/browse/QTBUG-66533
Attachments
Issue Links
- relates to
-
QTBUG-66533 declarative_ui::MouseArea::test_enabled fails in CI when run together with other tests
-
- Closed
-