Fix: don't apply inertial scrolling if input device is a mouse. #268284
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e is actually a touchpad, not a mouse
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR fixes an issue where inertial scrolling was being applied to mouse wheel input, causing excessive scrolling speed. The fix adds a condition to prevent inertial scrolling when the input device is detected as a physical mouse wheel.
Key changes:
- Added mouse wheel detection check to inertial scrolling condition
- Preserves inertial scrolling for non-mouse input devices (touchpads, touch screens)
bpasero
approved these changes
Oct 5, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a quick fix for #256269, where, if inertial scrolling is active, mouse scrolling becomes too fast.
Original pull request for inertial scrolling: #244034
@alexdima tagging you because you seemed to have been the code owner of this last time!