fix: Improve initial block placement#9903
Merged
Merged
Conversation
mikeharv
approved these changes
May 21, 2026
mikeharv
approved these changes
May 21, 2026
Collaborator
|
@gonfunko I think this has negative impacts on dragging blocks from the flyout with the mouse. |
Contributor
Author
|
Ah good catch, working on a fix forward |
1 task
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
Resolves
Fixes #9878
Proposed Changes
This PR improves the placement of newly-inserted blocks when using keyboard navigation. It's a near-exact backport of the logic from the keyboard-experimentation repo, with the adjustment of increasing the bounds of existing blocks to avoid placing the new block within snapping range. Generally new blocks will be placed wherever free space is available while scanning across the workspace row by row.