Bug 382058 - Can not scroll on a maximized window when cursor is on the margin
Summary: Can not scroll on a maximized window when cursor is on the margin
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: decorations (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-06 15:10 UTC by sedrubal
Modified: 2017-07-07 11:40 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:
mgraesslin: Wayland-
mgraesslin: X11+


Attachments
Scrolling using the mouse wheel is only possible if the cursor is inside the window (3.18 MB, video/ogg)
2017-07-06 15:10 UTC, sedrubal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description sedrubal 2017-07-06 15:10:25 UTC
Created attachment 106463 [details]
Scrolling using the mouse wheel is only possible if the cursor is inside the window

When you maximize a window with a scrollable content, you can't scroll anymore using the mouse wheel / touchpad gesture when the cursor is at the most left position of the screen.

The scrollable content of the window has to reach to the border of the window (like it is in Firefox, konqueror, konsole, ...).

It sound's a bit strange but it is very bad for UX if you're used to the behavior that you can always scroll in a maximized window even if the cursor is at the margin or the screen.

This may only be the outcome of an other change of kwins behavior.
Comment 1 Martin Flöser 2017-07-06 17:23:38 UTC
as a workaround disable the touch screen border. On Wayland this issue does not exist.

I mark the bug as wontfix as we got similar bug reports for it, but it's not a simple fix. Either we support touch screen borders and have this bug or we don't support them and don't have this bug. Anything more sophisticated would require a larger change in how this code works and that won't happen for a bug fix release.
Comment 2 sedrubal 2017-07-07 11:40:13 UTC
Thanks for figuring out the cause of the issue.

I'm not sure but I think I also had to disable active screen corners and edges.

I can understand that decision and it works for me.