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

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

--- Comment #12 from Scott Miles <sjmiles@chromium.org> ---
Dimitri was asked directly about 'sharing registries' and he said he thought
'no'.

On reflection, I believe this actually is the only answer that makes sense, but
it requires:

B: Current algorithm + Upgrade "yet-to-be-upgraded" elements when 
   it is inserted into the document.

Examples below are given in terms of <template> because it's encapsulating
document shenanigans, but I believe this is WLOG to doing it by hand.

Example:

<template>
   <x-foo></x-foo>
</template>

<x-foo> lives in a document fragment with no definition of x-foo, so it is
'plain'. The only chance then to upgrade x-foo is when I insert it into the 
main document.

This is sane, because it would be wasteful to upgrade <x-foo> in the document
fragment (it must be inert, after all) and in any case it would need to be
'custom-cloned' (i.e. re-initialized).

I believe this would work similarly for imports.

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

Received on Monday, 1 April 2013 23:34:32 UTC