Re: [selectors-api] Why null as opposed to empty string (or either one) to resolve default namespace from Boris Zbarsky on 2008-07-11 (public-webapps@w3.org from July to September 2008)

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Fri, 11 Jul 2008 16:14:54 -0400
To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
CC: public-webapps@w3.org
Message-ID: <4877BF3E.8060106@mit.edu>

Lachlan Hunt wrote:
>> The editor's draft changes the spec to require passing null instead of 
>> "" to resolve the default namespace.  I was just wondering why (it's a 
>> bit more of a pain to implement for me, and doesn't seem like a useful 
>> change, but maybe there's a reason I'm missing.
> 
> This was changed to be compatible with Node.lookupNamespaceURI(), which 
> requires null to be passed to get the default namespace.

Ah, ok.  I see.

For what it's worth, it looks to me like Gecko returns the default 
namespace if "" is passed to lookupNamespaceURI.  It's not clear to me 
whether that's correct per the DOM3 Core spec.

I do agree that having these two things be compatible is a good thing.

-Boris

Received on Friday, 11 July 2008 20:15:39 UTC