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

[Bug 23532] Dealing with undefined

From: <bugzilla@jessica.w3.org>
Date: Fri, 18 Oct 2013 16:20:26 +0000
To: public-script-coord@w3.org
Message-ID: <bug-23532-3890-bDIHjy1LqE@http.www.w3.org/Bugs/Public/>

--- Comment #11 from Boris Zbarsky <bzbarsky@mit.edu> ---
> Consensus was reached between representatives of all major implementors

With all due respect, the people representing SpiderMonkey there have nothing
to do with the methods this bug is talking about changing.  In particular, they
do not have any idea of what the compatibility constraints, if any, are.  So
their consensus on the ES behavior doesn't mean much for the DOM,

As far as the DOM goes, we've so far failed to make the change of treating
undefined as "not passed, use default value" for optional arguments: it's run
into compat issues in at least two cases.  We may be able to work around those
on the DOM side by modifying the IDL to not use optional arguments (for one we
can; for the other it's not even clear yet which API is involved, so it's hard
to tell), but there might be more.  It'll be a long slog, with broken websites
galore, before the fallout from that change settles, I suspect.

For the case in this bug, it's hard to say anything about compat impact until
someone tries it....

You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 18 October 2013 16:20:28 UTC

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