W3C home > Mailing lists > Public > public-webapi@w3.org > May 2008

Re: [WebIDL] Passing null and undefined to DOMString things

From: Cameron McCormack <cam@mcc.id.au>
Date: Tue, 20 May 2008 22:14:22 +1000
To: public-webapi@w3.org
Message-ID: <20080520121422.GC16728@arc.mcc.id.au>

Lachlan Hunt:
> The spec now states for [Null]:
>
>  "Otherwise, if the argument to [Null]  is Null, then the value assigned
>   to the attribute or passed as the operation argument will be the
>   string "null".
>
> That seems inconsistent with what you just wrote, and also inconcistent  
> with [Undefined], where it states:
>
>   "Otherwise, if the argument to [Undefined]  is Null, then the value
>    assigned to the attribute or passed as the operation argument will be
>    the null value."
>
> Did you intend for both to say "... the operation argument will be the  
> null value."?

I sure did.  (Fixed now.)

Thanks,

Cameron

-- 
Cameron McCormack ≝ http://mcc.id.au/
Received on Tuesday, 20 May 2008 12:24:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 20 May 2008 12:24:43 GMT