Potential compatibility with shadow DOM #2083
Draft
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
When using custom elements, needs to create icons again when inside of shadow DOM. Shadow DOM invisible from document selectors, so can't be replaced directly.
|
@unit-404 Cool idea! Maybe we can also test this with libraries like Lit. |
|
About get working, I did it in separate code (re-wrap). I.e. re-created that function. |
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.
When using custom elements, needs to create icons again when inside of shadow DOM. Shadow DOM invisible from document selectors, so can't be replaced directly. There is no new any icon.
What is the purpose of this pull request?
Description
Adds
rootElementfield forcreateIcons(default, isdocument).Before Submitting