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: Wed, 16 Oct 2013 15:15:50 +0000
To: public-script-coord@w3.org
Message-ID: <bug-23532-3890-D3frgzQf4k@http.www.w3.org/Bugs/Public/>

Glenn Maynard <glenn@zewt.org> changed:

           What    |Removed                     |Added
                 CC|                            |glenn@zewt.org

--- Comment #5 from Glenn Maynard <glenn@zewt.org> ---
FYI, I was thrown off a bit by the IRC conversation.  The discussion started
with "you can't make CSS.escape throw for missing arguments, that's not how
JavaScript works" (http://krijnhoetmer.nl/irc-logs/whatwg/20131016#l-409),
which ended in "we can do this as long as we make sure it throws if undefined
is passed in too".  Actually, tons of functions throw for missing arguments
already (WebIDL, and passing undefined isn't the same as not passing
an argument, so the discussion didn't make any sense.

This ticket is different: it's saying to change all of those existing required
arguments to throw if undefined is passed in.  That seems trivially better
(passing undefined to xhr.open() and opening "undefined" is never what you
meant to do), but I'm not sure it's worth the churn if there's already interop.

You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 16 October 2013 15:15:55 UTC

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