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: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Fri, 04 Oct 2013 11:20:03 -0400
Message-ID: <524EDCA3.5090308@mit.edu>
To: Anne van Kesteren <annevk@annevk.nl>
CC: Joshua Bell <jsbell@google.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>
On 10/4/13 11:14 AM, Anne van Kesteren wrote:
> 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.

True, I guess.

> Having said that, it's not clear we use
> TreatUndefinedAs today. It's not in DOM or HTML.

Interesting.  I thought there were uses, but I'm not obviously seeing 
any in the objects we've converted to WebIDL in Gecko so far.

Maybe we don't need any sort of TreatUndefinedAs at all... ;)

-Boris
Received on Friday, 4 October 2013 15:20:37 UTC

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