Re: [w3c/webcomponents] [Custom]: Callback for cloneNode/importNode (bugzilla: 24570) (#176)

I'll take a stab at it...

[cloneNode](https://dom.spec.whatwg.org/#concept-node-clone), insert a step after 2.1 which does something like: if node is a defined custom element, enque a custom element clone reaction in *_copy_'s queue* with node, definition, copy.

This idea of enqueueing in a random element's queue (it may not have a definition!) is new, but it will be useful if we investigate the "custom attributes/global attributes" thing. The reason you want to use that queue, and not the queue of the source node being cloned, is because the queues are there to deliver callbacks in a consistent order from the element-centric point of view the custom element author has. If you put the clone callback in the queue of the source node being cloned, convenient as it is, it will mean the cloned data will arrive at a "random" point of time from the point of view of the copy.

The cloned callback reaction will invoke something called clonedCallback from the source _node_'s definition; this is source _node_; there's one argument: _copy_.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/176#issuecomment-248846404