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
