Re: [XHR2] undefined as user/password arguments

On 4/11/12 6:57 AM, Jonas Sicking wrote:
> open(DOMString method, DOMString url, optional boolean async, optional
> DOMString? user, optional DOMString? password);
>
> This means that if anything other than null is passed as value for the
> user/password arguments, then the value should be stringified per
> normal WebIDL/ECMAScript rules. This includes if the value undefined
> is passed

That's not correct.  For nullable types, ES undefined is converted to 
IDL null per step 3 of 
<http://dev.w3.org/2006/webapi/WebIDL/#es-nullable-type>.  There's some 
extra complexity there around DOMString in step 1, but it only applies 
when [TreatUndefinedAs] is used, which it's not in this case.

-Boris

Received on Wednesday, 11 April 2012 16:27:10 UTC