fix: Custom Elements support for getActiveElement #6653
Closed
Conversation
This file contains 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
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
vtsvetkov-splunk
changed the title
|
Superseded by be95f49 – a simpler implementation. Tagged you as a co-author, @vtsvetkov-splunk . |
4 tasks
|
Released as part of 9.5.5. |
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.
Before changes:
Focusing shadowRooted input vs regular input
After changes:
Unfortunately, that would not work if shadowRoot has closed mode. In this case internals of the custom element is not accessible via an external document.
The issue is described here: Shadow DOM v1 - Self-Contained Web Components.
Should we check recursively?
Resolves #6652