[Bug 20488] [Custom]: Need to define what happens when nodes are adopted into or out of documents that have custom element definitions

https://www.w3.org/Bugs/Public/show_bug.cgi?id=20488

--- Comment #6 from Dimitri Glazkov <dglazkov@chromium.org> ---
(In reply to comment #5)
> (In reply to comment #4)
> > Okay, starting with the easy ones: cloning a node sort of works as spec'd.
> > The step 2 of http://dom.spec.whatwg.org/#concept-node-clone says "Let copy
> > be a node that implements the same interfaces as node". This implies
> > (probably) that a new node is constructed using steps from createElementNS
> > or something, which means that the we'll just get a different element
> > interface if new node document's registration context is different.
> 
> How does getting a different element interface cohere with "implements the
> same interfaces"?

It doesn't, that's the "sort of" part :) Do you think we need to monkeypatch
this in Custom Elements spec?

> Unrelated, but I was thinking a bit about adoptNode today. If that node is
> removed from its original document, does the leftDocument callback run?
> Since that happens after the DOM operation but before returning to script,
> does this mean there's a time when the element is in the new document, but
> with the old prototype? Or maybe there is no removed callback? (There's no
> _death_ callback, so it might be reasonable.)

Right. I think we should understand what transition between registration
contexts looks like. It's starting to look like death+birth to me.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 12 July 2013 19:27:28 UTC