Re: Possible compat problem with treating undefined as not passed in WebIDL from Anne van Kesteren on 2013-10-04 (public-script-coord@w3.org from October to December 2013)

From: Anne van Kesteren <annevk@annevk.nl>
Date: Fri, 4 Oct 2013 09:14:18 +0200
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: Joshua Bell <jsbell@google.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>
Message-ID: <CADnb78h36KNH6tn-xBxUD=JYxUGpgwqHZ8r=9brNL8emKh6ebg@mail.gmail.com>

On Thu, Oct 3, 2013 at 11:03 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 10/3/13 2:25 PM, Joshua Bell wrote:
>> The developer feedback on the APIs I've worked on is very strong that
>> passing undefined is expected to behave the same behavior as not passed
>
> I agree.  I think this is a good idea in general; we just need to adjust the
> XHR spec and keep an eye out for similar problems...

So should I add [TreatUndefinedAs=false]?


-- 
http://annevankesteren.nl/

Received on Friday, 4 October 2013 07:14:46 UTC