Skip to content
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

Define how shadow DOM should be handled when host is adopted to a new document #182

Closed
hayatoito opened this issue Jul 6, 2015 · 3 comments

Comments

@hayatoito
Copy link
Contributor

Title: Define how shadow DOM should be handled when host is adopted to a new document (bugzilla: 27366)

Migrated from: https://www.w3.org/Bugs/Public/show_bug.cgi?id=27366


comment: 0
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=27366#c0
Olli Pettay wrote on 2014-11-19 12:15:46 +0000.

The spec doesn't say what should happen to shadow DOM
if host is adopted to a new document.

The spec does have "The ownerDocument property of a node in a shadow tree must refers to the document of the shadow host which hosts the shadow tree."
but that misses 'adopting steps' from DOM spec which HTML relies on.

@hayatoito
Copy link
Contributor Author

@annevk , I think this issue now should be addressed by DOM Standard directly.

@annevk
Copy link
Collaborator

annevk commented Mar 17, 2016

@hayatoito does it match your understand that in https://dom.spec.whatwg.org/#concept-node-adopt I would change "inclusive descendant" to https://dom.spec.whatwg.org/#concept-shadow-root-including-inclusive-descendant. That way all the associated shadow trees would be adopted too. I'm assuming that's what's implemented.

@annevk annevk self-assigned this Mar 17, 2016
@annevk annevk changed the title Define how shadow DOM should be handled when host is adopted to a new document (bugzilla: 27366) Define how shadow DOM should be handled when host is adopted to a new document Mar 17, 2016
@hayatoito
Copy link
Contributor Author

Perfect. That would match my understanding and the implementation. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants