W3C home > Mailing lists > Public > public-webapi@w3.org > May 2008

Re: [selectors-api] Extended Attribute [NoNull] in the IDL

From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Date: Sat, 03 May 2008 02:49:09 +0200
Message-ID: <481BB685.6030701@lachy.id.au>
To: Boris Zbarsky <bzbarsky@MIT.EDU>
Cc: "Web APIs WG (public)" <public-webapi@w3.org>

Boris Zbarsky wrote:
> Lachlan Hunt wrote:
>>> What do they do if there is an element named <null> in the 
>>> document?
>> 
>> IE 8 Beta: Returns null or empty NodeList
> 
> Interesting.   What happens in IE8b1 if you do:
> 
>   document.querySelector("")

Throws a SYNTAX_ERR.

>> Opera: Returns the <null> element, or a NodeList with all of 
>> them. Similarly for undefined.
> 
> You mean document.querySelector(undefined) matches <undefined> nodes, 
> right?  That would be consistent with a JS 
> Object.prototype.toString() happening on the argument, I guess.

Yes.

> It's not clear to me how "undefined" should behave with the "NoNull" 
> decoration, for what it's worth.

Yeah, the bindings spec is very unclear about the whole thing.

-- 
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Received on Saturday, 3 May 2008 00:49:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 3 May 2008 00:49:47 GMT