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

Re: Possible compat problem with treating undefined as not passed in WebIDL

From: Jonas Sicking <jonas@sicking.cc>
Date: Thu, 3 Oct 2013 22:56:20 -0700
Message-ID: <CA+c2ei8u=aWOG+JU=u+M3kMB5Um20y5aOVLW+=URurqVAE9qng@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: Joshua Bell <jsbell@google.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Anne van Kesteren <annevk@annevk.nl> 
On Thu, Oct 3, 2013 at 2:03 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 10/3/13 2:25 PM, Joshua Bell wrote:
>>
>> Having an optional boolean argument default to "true" seems like poor JS
>> API design for this reason.
>
> Agreed.

We could always try to get data on how common passing 'undefined' as
third argument is and see if it's uncommon enough that we can phase it
out (with warnings and whatnot at first).

But like others, XHR has been around for long enough, and is commonly
used enough, that is seems unlikely that we can change anything here.

/ Jonas
Received on Friday, 4 October 2013 05:57:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:18 UTC