[Bug 27017] [Custom]: Constructor/prototype linkage needs to actually be defined, since it's dynamic, not static

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

--- Comment #2 from Boris Zbarsky <bzbarsky@mit.edu> ---

> Yep, that's exactly what it means.

There's a difference.  The Web IDL setup is about standard objects that are
created as part of the initial scripting environment setup.  Therefore it
doesn't have to specify how the properties are actually set/added/whatever
because it doesn't matter: none of the objects have any properties before the
set/add, there are no page-defined things on the prototypes, etc.

> This is already spec'd here: http://w3c.github.io/webcomponents/spec/custom/#dfn-custom-element-constructor-generation

Ah, step 1?  That covers it being already registered or having a
non-configurable property named "constructor", but doesn't cover what should
happen if it _is_ configurable.  If the intent is that a [[DefineOwnProperty]]
happens somewhere in here, that needs to be clearly specified.  Especially
because [[DefineOwnProperty]] can have side-effects, so you have to define how
it's ordered with other things.

Furthermore, you need to define exactly how one is supposed to determine "has a
non-configurable property named constructor".  I assume the intent is to do
[[GetOwnProperty]] and then check the [[Configurable]] of the resulting
property descriptor, but since this too can have side effects it's worth
specifying exactly how and when it happens.

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

Received on Friday, 10 October 2014 16:37:07 UTC