-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Expected behavior for importNode,cloneNode #1888
Comments
Thanks for posting this. This is a known limitation that comes with using Shady DOM. We need to add support for |
Marking this high priority since we plan to add these api's very soon. |
Great thanks for the feedback. |
After further investigation, separate issue #2010 is opened. |
I am not sure if this is by design and/or if it is a
Polymer
or rather a generalWeb-Components
spec issue.When I use
importNode
orcloneNode
withdeep=true
of a custom-element that contains another custom element (via Light DOM) and then insert it into the document, the resulting DOM structure is not the same as if I would create it manually.See the jsbin: http://jsbin.com/haxeni/edit?html,console
The text was updated successfully, but these errors were encountered: