fix(material/autocomplete): render overlay next to trigger #32282
Conversation
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
Switches to rendering the autocomplete's overlay next to the trigger. This resolves some long-standing accessibility issues, because previously the overlay wasn't in the tab order.
crisbeto
force-pushed
the
autocomplete-inline-overlay
branch
from
7035a9f to
3f054ac
Compare
andrewseguin
approved these changes
Nov 13, 2025
Member
Author
crisbeto
added a commit
that referenced
this pull request
Nov 13, 2025
Switches to rendering the autocomplete's overlay next to the trigger. This resolves some long-standing accessibility issues, because previously the overlay wasn't in the tab order. (cherry picked from commit b33af6b)
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.
Switches to rendering the autocomplete's overlay next to the trigger. This resolves some long-standing accessibility issues, because previously the overlay wasn't in the tab order.