https://bugs.kde.org/show_bug.cgi?id=394772
Vlad Zahorodnii <vlad.zahorod...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma/kwin/-/commit/ec5a0249e2 |ma/kwin/commit/617adda2911e
|6acdf12677df535df3d3faa6a18 |08cef70e110b3125e7d3f60498d
|b49 |1
--- Comment #34 from Vlad Zahorodnii <vlad.zahorod...@kde.org> ---
Git commit 617adda2911e08cef70e110b3125e7d3f60498d1 by Vlad Zahorodnii.
Committed on 28/07/2020 at 07:21.
Pushed by vladz into branch 'Plasma/5.18'.
[x11] Hold a passive grab on buttons only when needed
Due to a bug in the XI2 protocol, clients have to reset scroll valuators
on XI_Enter because the scroll valuators might have changed while the
pointer was elsewhere. The XI_Enter event is usually sent when an input
device enters the window, but it can also be generated by a passive grab.
If an XI_Enter event has been generated by a passive grab, the client
should not reset scroll valuators. Unfortunately, there is no any
reliable way for the client to determine if an XI_Enter event has been
sent in response to a deactivated passive grab. A correct fix for the
scroll issues in GTK apps would involve changes in the XI2 protocol.
As a work around, we can hold a passive grab only if the current mouse
wheel action is either "Activate and scroll" or "Activate, raise, and
scroll."
FIXED-IN: 5.19.3
(cherry picked from commit ec5a0249e26acdf12677df535df3d3faa6a18b49)
M +68 -45 events.cpp
M +3 -0 options.h
M +1 -0 x11client.cpp
M +2 -2 x11client.h
https://invent.kde.org/plasma/kwin/commit/617adda2911e08cef70e110b3125e7d3f60498d1
--
You are receiving this mail because:
You are watching all bug changes.
