- From: <bugzilla@jessica.w3.org>
- Date: Fri, 07 Jun 2013 04:34:51 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21825 --- Comment #2 from Dominic Cooney <dominicc@chromium.org> --- (In reply to comment #1) > I am probably reading this wrong, but don't we only create new elements in > cloneNode? I don't think appendChild or adoptNode do that. Ah... in legacy DOM appendChild may fall back to adoptNode if the node is in a different document, and adoptNode may fall back to doing importNode depending on implementations, and importNode creates an element. In DOM4 it looks like that adoptNode->importNode fallback does not exist. Great. But we need to handle cloneNode and importNode. In fact, DOM4 has a concept for "clone" <http://dom.spec.whatwg.org/#concept-node-clone> -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 7 June 2013 04:34:53 UTC