Important change in WebIDL (Was: [Bug 10640] Allow for non-nullable objects)

Hi,

The Web IDL spec has just integrated a change that introduces a fairly
big backward-incompatibility: up until now, the declaration
        interface Foo {
          attribute Bar myAttribute;
        }
implied that "null" was a valid value for myAttribute (since interface
objects were always nullable).

After the change described below, this is no longer the case, and
nullability needs to be made explicit, à la 
 interface Foo {
          attribute Bar? myAttribute;
        }

(this applies as well to method arguments and return types)

This like affects most of our APIs, and most certainly the Contacts API
(which I now note is lacking the nullability marker on attributes of the
Contact Interface)

Dom

-------- Message transféré --------
> De: bugzilla@jessica.w3.org
> À: public-webapps@w3.org
> Sujet: [Bug 10640] Allow for non-nullable objects
> Date: Mon, 23 May 2011 00:27:31 +0000
> 
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=10640
> 
> Cameron McCormack <cam@mcc.id.au> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|NEW                         |RESOLVED
>          Resolution|                            |FIXED
> 
> --- Comment #4 from Cameron McCormack <cam@mcc.id.au> 2011-05-23 00:27:30 UTC ---
> Done:
> http://dev.w3.org/cvsweb/2006/webapi/WebIDL/Overview.xml.diff?r1=1.269;r2=1.270;f=h
> 
> -- 
> Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
> 
>

Received on Monday, 23 May 2011 06:58:48 UTC