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 17:14:05 +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: <CADnb78ghPzYeLReMwSFczwmXigZ1w=w9Z98qktNrJErAJNWD0g@mail.gmail.com>

On Fri, Oct 4, 2013 at 2:05 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> For this specific one-off case, I'd rather we added the two overloads and a
> bit of prose instead of adding more [TreatUndefinedAs] complexity.

So the other values are EmptyString and Null. We could make those ""
and null and then they would actually be useful values you could
generate code from. Having said that, it's not clear we use
TreatUndefinedAs today. It's not in DOM or HTML.

-- 
http://annevankesteren.nl/

Received on Friday, 4 October 2013 15:14:36 UTC