docs: fix documentation on changing max dropdown height - #10319
Merged
zspriggs merged 1 commit intoAug 25, 2026
Conversation
lizschwab
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 #8147
Proposed Changes
Adds documentation on how to set max height of dropdown field.
Reason for Changes
The docs previously described using a property (
Blockly.FieldDropdown.MAX_MENU_HEIGHT_VH) that has since been completely refactored out.Test Coverage
n/a
Documentation
n/a
Additional Information
It might be a slightly specific scenario that someone a) would want to adjust the max height of field dropdowns, b) use a plugin that extends the
FieldDropdownclass, and c) care that they are both affected by changingmax-height.I was going back and forth on whether to provide the workaround using
:has()of if the section should just end by stating that overridingmax-heightmight affect plugins. I erred on the side of caution and kept it in, but can remove if it doesn't seem applicable enough.