W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2012

Re: Why do WebIDL dictionary members not have [TreatNullAs], [TreatUndefinedAs] apply to them?

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Thu, 07 Jun 2012 10:43:49 -0400
Message-ID: <4FD0BE25.4090903@mit.edu>
To: Anne van Kesteren <annevk@annevk.nl>
CC: Cameron McCormack <cam@mcc.id.au>, public-script-coord@w3.org
On 6/7/12 10:22 AM, Anne van Kesteren wrote:
> I guess having these supported as part of the browser engine does not
> matter much.

Oh, I think it does.

> It's mostly new specifications we care about. As long as
> those don't use it

The only way to enforce that people don't use things like this, really, 
is for browsers not to support them...  In my opinion.

In particular, there's tons of invalid WebIDL in specs out there.  Every 
time I try to run a new spec through our WebIDL parser so far, I find a 
bunch of bugs in it, because the parser is in fact validating the 
various correctness requirements WebIDL has.

Since I would like the parser to continue doing that, I need to either 
implement this restriction or the spec needs to lift it.  ;)

Received on Thursday, 7 June 2012 14:44:25 UTC

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