- From: <bugzilla@jessica.w3.org>
- Date: Mon, 10 Feb 2014 15:31:15 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24570 --- Comment #4 from Erik Arvidsson <arv@chromium.org> --- I was in a rush when filing this. Conceptually I think we need to be able to explain how the built ins work in this area but I didn't think much about it at the time. I agree that http://dom.spec.whatwg.org/#concept-node-clone-ext is the concept we want to achieve. I'm not sure why you think "insertion has already happened". I think the order would be something more aligned to. New Node - Created Callback Old Node - Cloning Step Callback ... New Node - Attached Callback (if ever inserted into a document) I think the above would work for script. The cloning step would copy the "already started" flag and the attached callback would check if it set. The semantics of this callback would be to call it as a last step of http://dom.spec.whatwg.org/#concept-node-clone and call the callbacks in document order in the cloned tree, passing the old node as the context object and the new node as the only argument (the document can be reached through ownerDocument if needed). -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 10 February 2014 15:31:18 UTC