-
Notifications
You must be signed in to change notification settings - Fork 378
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
Detecting finally-distributed nodes. #675
Comments
That issue is closed, so this re-opens it. I think this is a legitimate issue, useful for people who want to do custom rendering, as they need to render based on the composed tree. Leaving this issue open and providing needed API changes will encourage custom elements authors (f.e. A-Frame authors) to support ShadowDOM (currently A-Frame does not work with ShadowDOM), and thus will help bring Web Components forward. Do you prefer discussion in closed threads? People often associate closed threads with ideas that were decided to be not worth pursuing. |
Unless there is a new idea or a new proposal, I don't think filing a new issue for a closed issue is a good idea. It's still unclear to me that what is new in this issue. |
Closing per last comment. |
This is a new issue for the idea mentioned here: #611 (comment).
It is useful to know when nodes are finally-distributed (knowing when distributed nodes ultimately rest at a slot and are not forwarded to any more slots).
The text was updated successfully, but these errors were encountered: