Bug 372669 - Chrome scroll bar snaps back when ending scroll bar drag with cursor outside the window
Summary: Chrome scroll bar snaps back when ending scroll bar drag with cursor outside ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: git master
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-11-19 16:10 UTC by Kai Uwe Broulik
Modified: 2018-10-27 01:59 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Uwe Broulik 2016-11-19 16:10:43 UTC
(Besides the fact that scrollbar snapback breaks Fitts' law in spectacular ways and no toolkit on Linux besides Aura does it)

When you drag the scroll bar in a Chrome window (xwayland) and release the mouse button with the mouse outside the Chrome window whilst keeping the mouse close enough so it doesn't snap back, it will snap back to the previous scroll position nonetheless after you released the mouse.

1.) Open Chrome in a Wayland session and open some website
2.) Resize the window so there's a vertical scrollbar and make the window non-maximized (or add a top panel)
3.) Press and hold the scroll bar with the mouse
4.) Now scroll in any direction
5.) Move the mouse outside the Chrome window but keep it close enough so Chrome doesn't already automatically snap back
6.) Release mouse button

If the mouse hovers another X window (doesn't need to be a Chrome window, can be any Xwayland client, just stack it behind the Chrome window) then releasing the mouse while over that window won't snap it back.

It seems that the mouse release event doesn't get proper coordinates because X only gets the mouse position while inside an X client? Or don't we even set the X cursor back to 0,0 to ensure hover effects and what not reset?
Comment 1 Martin Flöser 2016-11-19 17:26:34 UTC
Please try again with XWayland 1.19. I consider it as likely to be fixed there.
Comment 2 Andrew Crouthamel 2018-09-26 22:25:04 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-10-27 01:59:48 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!