[Bug 21485] [Custom]: Consider possible candidates of element upgrade

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

--- Comment #14 from Scott Miles <sjmiles@chromium.org> ---
An alternative notion has been floated that could work with answer 'A'.

The idea is that when, e.g., templates are instantiated, the correct node is
generated at creation time (as long as the nodes are created with the proper
document owner).

I believe the advantage of this idea is that upgrade is decoupled from
adoption/insertion.

In the general case however, cloneNode has no notion of 'target document' to
make this work. I also expect users to want to migrate subtrees from imports to
the main document, and expect the custom elements to generate.

Sidebar: the notion of A may require that some custom elements take care to
operate only on insertion, and even then only in suitable contexts. I don't
claim this is a problem however, because this is a normal condition for DOM
nodes. For example, <img src='foo.jpg'> tag doesn't actually hit the network to
load 'foo.jpg' until it's in a suitable document context.

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

Received on Tuesday, 2 April 2013 01:10:58 UTC