GNOME Bugzilla – Bug 784879
Unpredictable actions from scrollbar drag on non-maximized window
Last modified: 2017-12-01 07:50:42 UTC
Say you have a non-maximized window, such as epiphany or nautilus. Begin dragging the scrollbar, but let your mouse move outside the direct child of the window while dragging (happens frequently for me with ThinkPad touchpoint). When the pointer falls outside of the shadow area of the window, events stop being delivered to the target window and the scroll stops. Furthermore, if you have moved your mouse over an area of another background window, releasing the pointer will be synthesized into a GtkButton::clicked event if it has fallen over a button. I've only tested on Wayland, but I'm pretty sure the event delivery model in X would continue delivering events to the scrollbar while it holds a grab.
this bug is basically complaining that wayland has no grabs.
Humm, works just fine here. Mouse button press on the scrollbar, move pointer outside the surface while keeping the button depressed, move pointer up and down and the scrollbar follows even when the pointer is outside the surface. I tried with gedit, nautilus and epiphany...
(In reply to Olivier Fourdan from comment #2) > Humm, works just fine here. Didn't Carlos implement grabs since this was reported?
(In reply to Christian Hergert from comment #3) > Didn't Carlos implement grabs since this was reported? Wayland has no support for explicit grab (not to be confused with the shortcuts inhibitor protocol) and implicit grabs have always been there, at least as far as my memory serves :) If anything, the fix for this particular issue is actually in mutter and is most likely commit 5db48fac: wayland: Update button state on motion/button events More specifically, avoid crossing events, since clutter does not set modifier/button state on those. Fixes implicit grabs being broken when the pointer moves past the surface boundaries. https://bugzilla.gnome.org/show_bug.cgi?id=785347 I think it is safe to mark this bug as a duplicate of bug 785347 *** This bug has been marked as a duplicate of bug 785347 ***