fix: Fix chaotic glitchiness when using scroll options with keyboard moves#2732
Merged
Conversation
lizschwab
approved these changes
Jun 25, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
The basics
The details
Resolves
Fixes #2710
Proposed Changes
This PR updates the scroll-options plugin's
Draggersubclass to be a no-op during keyboard-driven drags. This prevents its behavior and the built-in behavior of moving the workspace when a keyboard-driven block drag reaches the bounds from fighting and causing visual glitches with the scroll position and move indicator. The built-in behavior for keyboard-driven drags is what the plugin provides for mouse-driven drags, so having the plugin disable itself during keyboard drags yields effectively the same behavior as it normally provides.