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

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

--- Comment #1 from Scott Miles <sjmiles@chromium.org> ---
My initial reactions:

I could live in a world where outOfDocElement is simply never upgraded; in
general I'm willing to accept some resposibility for timing of actions. From
this standpoint, it's all a matter of how costly each option is to implement.

A. upgrade all: is probably best, but since Morrita-san says it causes trouble,
I'm ready to dismiss it.
B. upgrade on insertion: would probably be a good compromise.
C. document.upgrade(): my sense is to avoid this complication.
D. do nothing: simple may be best, as suggested.

>> What does happen when a custom element, which lives in a document D1, is inserted to different document D2 <<

IMO, nothing at all. I suspect user wants the behavior element had in D1 to be
transferred to D2. I realize this creates a weird situation wrt localName. I
would rather somehow alter localName then morph the element. Another
possibility is to just make it an error.

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

Received on Monday, 1 April 2013 16:58:38 UTC