[Bug 23532] Dealing with undefined

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23532

--- Comment #13 from Boris Zbarsky <bzbarsky@mit.edu> ---
One more note: the change I describe sounds to me like putting theoretical
purity ahead of web developers, 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...  But
that wouldn't be the first time, I guess; as far as I can tell we have a
different priority of constituencies (though not spelled out) in TC39 than the
WHATWG and HTMLWG generally seem to.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Wednesday, 23 October 2013 13:59:13 UTC