[Bug 27016] [Custom]: Custom element constructor behavior makes no sense

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

--- Comment #4 from Boris Zbarsky <bzbarsky@mit.edu> ---
> No, I am defining F in that algo.

Ah.  So you're defining the steps that
http://people.mozilla.org/~jorendorff/es6-draft.html#sec-built-in-function-objects-call-thisargument-argumentslist
executes in step 9?

But then this thing is not an "interface object" in the Web IDL sense, as you
claim, because those in fact define different such steps.  We need to harmonize
this somehow.

In any case, if these are steps for step 9 of [[Call]] they still have the
problem I described.

> tries to do the thing you're describing below

I don't believe it succeeds, sorry.

> Would love any specific diffs/patches on how that could be made better.

My suggestion for how to do that is in comment 2: you say that this is a Web
IDL constructor and then define the "actions listed in the description" to
create and return an element with the right bits set.  It's pretty much what
you have, except instead of setting the (immutable) localName and namespace and
so forth of the element you want to do something similar to what
createElementNS does.

On a side note, step 3 of
http://w3c.github.io/webcomponents/spec/custom/#dfn-custom-element-constructor-generation
seems to be dead?  "REGISTRY" is never used...

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

Received on Friday, 10 October 2014 17:30:44 UTC