Repository navigation
fix: all use closest candidate when moving disconnected blocks - #9971
Merged
Merged
Conversation
maribethb
approved these changes
Jun 10, 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
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.
The basics
The details
Proposed Changes
This unifies the behavior of selecting the closest connection that is currently reserved for non-looping mode so that it happens in either mode.
Reason for Changes
Currently, when there is no current connection pair and we are looping, a block is moved to the first or last possible connection, depending on move direction. This causes an unexpected jump in block position for non-screenreader users.
Test Coverage
One test needed to be updated as this changes the required move commands to achieve a particular block arrangement.