- From: <bugzilla@jessica.w3.org>
- Date: Thu, 17 Jan 2013 00:32:08 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20486 --- Comment #3 from Cameron McCormack <cam@mcc.id.au> --- (In reply to comment #2) > > 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. Boris is right about this. Interfaces inherit from other interfaces; ECMAScript objects can implement interfaces. Interface prototype objects don't implement any interfaces. > > 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. I can't tell what spec this bug is about, so I don't know if this suggestion is exactly what you want, but maybe wording like this could work: Otherwise, if PROTOTYPE is not an interface prototype object for an IDL interface that inherits from HTMLElement, throw a TypeMismatchError exception. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 17 January 2013 00:32:09 UTC