W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2013

Re: [webidl] Spec for callback interface interface objects is self-contradictory in places

From: Cameron McCormack <cam@mcc.id.au>
Date: Fri, 02 Aug 2013 13:40:34 +1000
Message-ID: <51FB2A32.5050801@mcc.id.au>
To: Boris Zbarsky <bzbarsky@MIT.EDU>
CC: public-script-coord@w3.org
Thanks, both of these are fixed now:

Boris Zbarsky wrote:
> Section 4.3.8 says:
>
> The [NoInterfaceObject] extended attribute MUST NOT be specified on a
> callback interface, as interface objects never exist for callback
> interfaces.
>
> but section 4.4 says:
>
> For every interface that...
> is a callback interface that has constants declared on it, or...
> a corresponding property MUST exist on the ECMAScript global object.
> The name of the property is the identifier of the interface, and its
> value is an object called the interface object.
>
> I believe 4.3.8 is wrong here.

http://dev.w3.org/cvsweb/2006/webapi/WebIDL/Overview.xml.diff?r1=1.651;r2=1.652;f=h
http://dev.w3.org/cvsweb/2006/webapi/WebIDL/v1.xml.diff?r1=1.91;r2=1.92;f=h

> And then 4.4.1 defines interface objects for callback interfaces as not
> being function objects, but later on requires a "length" property on all
> interface objects. That looks wrong to me; the "length" thing should
> only happen for non-callback interface objects.

http://dev.w3.org/cvsweb/2006/webapi/WebIDL/Overview.xml.diff?r1=1.652;r2=1.653;f=h
http://dev.w3.org/cvsweb/2006/webapi/WebIDL/v1.xml.diff?r1=1.92;r2=1.93;f=h
Received on Friday, 2 August 2013 03:41:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:50 UTC