fix(teleport): correctly select overlay container in shadow DOM #20277
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.
Description
When VOverlay is mounted in the Shadow DOM, it passes correctly the shadowRoot element to the teleport composable. Then the teleport composable checks for an existing v-overlay-container using
:scope > .v-overlay-container
selector.However, as confirmed by css specs discussion, :scope selector doesn't select anything when used on a ShadowRoot element, so an existing overlay container is never found and it is created and appended again.
The solution is to use
:host > .v-overlay-container
selector when the element is an instance of ShadowRoot.fixes #20276
Markup: