
Loading…
Expected behavior for importNode,cloneNode #1888
timeu
commented
Owner
sorvell
commented
Thanks for posting this. This is a known limitation that comes with using Shady DOM. We need to add support for importNode and cloneNode to the Polymer.dom api to address this. At that point, you'll use Polymer.dom(element).cloneNode and Polymer.dom(element).importNode.
Owner
sorvell
commented
Marking this high priority since we plan to add these api's very soon.
timeu
commented
Great thanks for the feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am not sure if this is by design and/or if it is a
Polymeror rather a generalWeb-Componentsspec issue.When I use
importNodeorcloneNodewithdeep=trueof 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