- From: <bugzilla@jessica.w3.org>
- Date: Wed, 16 Jan 2013 18:07:42 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20486
Boris Zbarsky <bzbarsky@mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |cam@mcc.id.au
Resolution|INVALID |---
--- Comment #2 from Boris Zbarsky <bzbarsky@mit.edu> ---
> It's defined to be an interface prototype object
Ah... where does it say that? Is that the
"Otherwise, if PROTOTYPE does not inherit from the HTMLElement interface,
throw a TypeMismatchError exception."
bit?
> and WebIDL defines what "inherit" means in respect to interface prototype
> objects.
No, it doesn't. It defines what it means for an interface to inherit from
another interface, which is not the same thing.
> If WebIDL needs to firm out how this syntactic construct translates to
> ECMAScript better, then that's what we need to do.
That's fine, but that needs to happen then. Sweeping the issue under the rug
won't make it happen.
Again, this is not a theoretical issue. The one implementation of this spec
I've looked at certainly allowed any object that had HTMLElement.prototype on
its proto chain as the prototype here, so either it can in fact be a random
object or this implementation was wrong and the spec was not clear enough.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 16 January 2013 18:07:44 UTC