fix: Improve block placement when inserting from flyout via keyboard - #10318
Merged
Conversation
mikeharv
approved these changes
Aug 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 #10072
Proposed Changes
This PR improves the placement of blocks inserted from the flyout via the keyboard. Previously, blocks would be tiled left to right, top to bottom from (0, 0). Now, tiling starts from the top left (in LTR) or top right (in RTL) of the workspace's visible viewport, and proceeds right-to-left in RTL mode. This provides the spatially-expected behavior, and tiles blocks in the entire visible viewport without jumping the scroll position around.