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

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

Rafael Weinstein <rafaelw@chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rafaelw@chromium.org

--- Comment #19 from Rafael Weinstein <rafaelw@chromium.org> ---
So it seems to me that the *most* sanity results from the strongest guarantee:

->Script should never have access to an un-upgraded custom element.

Deviation from this invariant exposes a fracture in the mental model that page
script may implement host (DOM) elements.

This invariant is unachievable, as demonstrated in Morrita-san's original
example. I.e. since registration can happen at any time, script will always
have access to an un-upgraded element before it was registered.

However, a slightly less strong guarantee *is* possible:

->Script should never have access to an un-upgraded custom element, once the
identity of that element is known (i.e. it has been registered).

In my mind, anything short of this is a serious flaw in the processing model of
custom elements and falling short should have strong justification.

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

Received on Tuesday, 2 April 2013 21:51:35 UTC