Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.13.0, 5.13.1
-
Dell XPS 15 9560, Windows 10
-
-
23df1603f514407d245a2740f32f589318ef654e (qt/qtdeclarative/5.15) ff6bd91f580fa5ddae2d02f32b9d83be4374a445 (qt/qtdeclarative/5.12)
Description
Example code:
import QtQuick 2.13 import QtQuick.Controls 2.13 import QtQuick.Layouts 1.4 ApplicationWindow { visible: true width: 640 height: 480 title: qsTr("Scroll") Rectangle { width: 200 height: 200 color: mouseArea.pressed ? "red" : "blue" opacity: 0.6 MouseArea { //Similar problems occur if you change MouseArea to Button id: mouseArea anchors.fill: parent } } Rectangle { y: 100 z: -1 width: 200 height: 200 color: dragHandler.active ? "orange" : "green" opacity: 0.6 DragHandler { id: dragHandler } } }
Steps to reproduce of the error:
- Press and hold at the place where two rectangles overlap (MouseArea goes in pressed state)
- Drag (DragHandler will be active, but MouseArea / Button stay in pressed state)
- Release the mouse button
- MouseArea doesn't respond to clicks anymore.
Update: This only happens with a touch screen now, in 5.13.1 it was fixed as far as mouse input is concerned
Attachments
Issue Links
- relates to
-
QTBUG-75025 Button remains pressed if the DragHandler is under it
- Closed
-
QTBUG-77621 MouseArea stops working after using the wheel
- Closed
-
QTBUG-78258 DragHandler's grab permission CanTakeOverFromAnything does not respect keep grab
- Closed
For Gerrit Dashboard: QTBUG-77624 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
277041,2 | MouseArea: react to touch ungrab | 5.14 | qt/qtdeclarative | Status: MERGED | +2 | 0 |
277046,1 | React to touch ungrab via mouse ungrab in items that don't handle touch | 5.14 | qt/qtdeclarative | Status: ABANDONED | 0 | 0 |
282016,2 | MouseArea: react to touch ungrab | 5.12 | qt/qtdeclarative | Status: MERGED | +2 | 0 |