-
Notifications
You must be signed in to change notification settings - Fork 383
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Idea] Distant ShadowDOM. #576
Comments
Also see #574. |
This proposal would significantly worsens the performance characteristics of our shadow DOM implementation because ordering all those slotted elements in the tree order (or maybe insertion order?) would require O(n) traversal of the entire tree. |
Hmm. It is not clearly demonstrated what problem this idea is trying to resolve. @trusktr Unless there is a clear proposal, it might be difficult to discuss. |
Let me close this since it is not clearly demonstrated what problem this idea is trying to resolve. |
Currently, we can only distributed elements into a shadow root that is sibling to those elements. It'd be nice to be able to distribute elements into any shadow root, perhaps using an ID.
f.e.
In that example, the
span
would be distributed into the shadow root of#root-containing-element
.The reason I would want this is because it solves the problems that are introduced by me having to workaround the breaking changes of the css-transforms spec introduced in Chrome 53.
The text was updated successfully, but these errors were encountered: