Re: [WebIDL] Handling undefined in Overload Resolution Algorithm

On 8/4/11 12:38 PM, Anne van Kesteren wrote:
> On Thu, 04 Aug 2011 15:24:58 +0200, Boris Zbarsky <bzbarsky@mit.edu> wrote:
>> In Gecko, undefined used to be treated as "not specified" for
>> XMLHttpRequest. When we changed to following the current spec (which
>> converts undefined to "undefined") we actually ran into compat issues
>> with some popular JS libraries that pass undefined for
>> username/password explicitly. For now we're sticking it out, but it
>> sure would be nice to not have those compat issues!
>
> http://dev.w3.org/2006/webapi/XMLHttpRequest-2/ seems to just defer to
> IDL as far as I can tell. If the IDL or method descriptions need
> changing please let public-webapps@w3.org know.

It's not clear to me that there's a way to express the old 
(web-compatible, imo) behavior in idl.  That's what this discussion is 
about!

-Boris

Received on Thursday, 4 August 2011 17:22:26 UTC