- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Tue, 09 Oct 2012 21:17:39 -0400
- To: Joshua Bell <jsbell@chromium.org>
- CC: public-webapps <public-webapps@w3.org>, Alec Flett <alecflett@chromium.org>, Robert Ginda <rginda@chromium.org>
On 10/9/12 7:53 PM, Joshua Bell wrote: > The existence of an extended attribute in WebIDL to change the behavior > in this case hints at the need for both binding behaviors for > compatibility with the web. I note that there's no corresponding > TreatNullAs=Missing, however. Perhaps Cameron can jump in with any > details he remembers? No one asked for that behavior, because that's not how ES ever behaves. There is no problem allowing null values and defining behavior in prose for them, though, unlike undefined, which is not a first-class IDL value type. -Boris
Received on Wednesday, 10 October 2012 01:18:08 UTC