[GH-ISSUE #950] Ability to stop scroll events being sent to client if mouse position changes #762

New issue

Open

opened 2026-05-05 07:02:23 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 07:02:23 -06:00

Owner

Originally created by @vladubogdan on GitHub (Nov 16, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/950

Hello,

I would like the ability to stop the scroll events being sent to the client if the mouse is moved from the initial scroll position.

The following is an issue if you use Momentum/inertia scrolling.

MacOS is smart enough to know where you initiated the scroll and only scroll in that section. If you move to another scrollable section no scroll events will happen.
Please see this video I made to demonstrate this.
https://www.dropbox.com/s/iddykt2y39mcm79/osXScrollBehaviour.mov?dl=0

While on Windows 10 - the system does not care where you initiated your scroll. It will continue scrolling until the event is finished. You can restrict scroll to inactive windows in settings, but that will not stop this behaviour when you have different scroll regions in the same window.
Please see the video demonstrating windows 10 behaviour.
https://www.dropbox.com/s/i7t8p6nz5bft8c4/windows10ScrollBehaviour.mp4?dl=0

Explanation: In both videos I initiate scrolling in one section of the window and then move the mouse to another section - on OS X only the section where I initiated scroll moves while on Windows 10 all scroll sections move - no matter where I initiated the scroll.

My thinking here is that - a simple checkbox will fix this ugly windows 10 behaviour.
Save the position where the initial scroll event was started and if the position of the mouse changes by a delta bigger than 10px (lets say , could be configured) do not send the scroll events to the client.

Thank you!

Originally created by @vladubogdan on GitHub (Nov 16, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/950 Hello, I would like the ability to stop the scroll events being sent to the client if the mouse is moved from the initial scroll position. The following is an issue if you use Momentum/inertia scrolling. MacOS is smart enough to know where you initiated the scroll and only scroll in that section. If you move to another scrollable section no scroll events will happen. Please see this video I made to demonstrate this. https://www.dropbox.com/s/iddykt2y39mcm79/osXScrollBehaviour.mov?dl=0 While on Windows 10 - the system does not care where you initiated your scroll. It will continue scrolling until the event is finished. You can restrict scroll to inactive windows in settings, but that will not stop this behaviour when you have different scroll regions in the same window. Please see the video demonstrating windows 10 behaviour. https://www.dropbox.com/s/i7t8p6nz5bft8c4/windows10ScrollBehaviour.mp4?dl=0 Explanation: In both videos I initiate scrolling in one section of the window and then move the mouse to another section - on OS X only the section where I initiated scroll moves while on Windows 10 all scroll sections move - no matter where I initiated the scroll. My thinking here is that - a simple checkbox will fix this ugly windows 10 behaviour. Save the position where the initial scroll event was started and if the position of the mouse changes by a delta bigger than 10px (lets say , could be configured) do not send the scroll events to the client. Thank you!

No labels

Rows
Columns