[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 #9 from Dimitri Glazkov <dglazkov@chromium.org> ---
(In reply to comment #7)

> Implied weirdness #1: innerHTML no longer reliably round-trips things,
> because an element may have picked up a definition in a different context.
> As it is serialized and reparsed, the new element sloughs off that
> definition and picks up whatever is in the new context.

It's probably not a great consolation, but we already lost the battle with type
extensions:

div.setAttribute("is", "boom-tshack");
div.parentNode.innerHTML = div.parentNode.innerHTML;

I am leaning toward Planet 2 as well. There's discussion on bug 20567 that
could  be relevant.

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

Received on Friday, 19 July 2013 19:42:55 UTC