fix!: Flyout follows toolbox in DOM#9849
Merged
Merged
Conversation
lizschwab
approved these changes
May 11, 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
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 #9796
Proposed Changes
This change ensures that flyout appears in the DOM directly before the workspace in order to aid in tab navigation.
Reason for Changes
As reported by @microbit-robert:
Test Coverage
A new test ensures that the toolbox, flyout, and workspace are all contained in the injection div in the correct order. The ordering is relative rather than absolute in order to permit flexibility with other children, such as scrollbars.
BREAKING CHANGE
This change may affect you if you application relies on the specific child order of elements in the Blockly injective div.
Previously the DOM structure was:
It is now: