[Bug 20493] [Custom]: Need to define, not set the "constructor" property on element prototype.

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

--- Comment #3 from Dimitri Glazkov <dglazkov@chromium.org> ---
(In reply to comment #2)
> > Since this is a function object, it will already have the "prototype" property
> 
> The spec section you link to is what happens if you create a function from a
> string.  It's not applicable here, unless you explicitly invoke it in the
> components spec (in which case you have to define the inputs to that
> algorithm and whatnot.. but I suspect you do not in fact want to go there,
> since you want these to be [native code] functions).
> 
> You should really look into how WebIDL defines its constructor objects and
> ideally share that definition....

(In reply to comment #2)
> > Since this is a function object, it will already have the "prototype" property
> 
> The spec section you link to is what happens if you create a function from a
> string.  It's not applicable here, unless you explicitly invoke it in the
> components spec (in which case you have to define the inputs to that
> algorithm and whatnot.. but I suspect you do not in fact want to go there,
> since you want these to be [native code] functions).

There's a not at the end that simply states:

"A prototype property is automatically created for every function, to allow for
the possibility that the function will be used as a constructor."

Or is this not enough?

> 
> You should really look into how WebIDL defines its constructor objects and
> ideally share that definition....

Yup. And probably file bugs against WebIDL.

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

Received on Friday, 11 January 2013 20:51:29 UTC