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

--- Comment #16 from Glenn Maynard <glenn@zewt.org> ---
(In reply to Domenic Denicola from comment #15)
> >  since I suspect web developers would prefer a clear indication that a call like document.body.setAttribute() (with no arguments) is incorrect instead of it silently doing something bogus...
> I don't think this is true, given the wide acceptance and prevalence of web
> developer-created libraries that do not do argument validation of this sort.
> (For example, jQuery.) Argument validation exceptions are not idiomatic to
> or expected by JavaScript code, generally.

Of course we want to be told when we're doing something that is blatantly
incorrect.  Libraries don't do it because it's cumbersome to do in JavaScript,
but that's a bug, not a feature.

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

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