Re: [w3c/DOM-Parsing] XML null namespaces need to be preserved (#47)

Anne -

---- "Is this a bug in the specification text? If so, where?"

It looks like this **might** be covered in section `3.2.1.1.1 Recording the namespace`, step 4.

@tkent-google Can you confirm? I'm not a specification person, sorry ;-). You know what I'm after here. Thank you!

---- "Is this a bug in implementations? If so, are there implementation bugs?"

I would note that, while currently Edge is out of compliance (until they switch to Chromium, obviously), all other currently-supported (not old IE) browsers support this construct. On IE, the old ActiveX DOM Parser did support this construct.

In fact, 14 years ago, I made this report about this very issue to the Mozilla team :-).

https://bugzilla.mozilla.org/show_bug.cgi?id=301260

---- "Is this tested by wpt?"

Those tests **might** cover the use case I'm talking about here. Obviously, due to the fact that this feature really has to do with 'escaping' elements from the surrounding default namespace context, having tests exercising that would be ideal. I think that would require adding tests to the DOMParser side of the house to make sure that the value of the `.namespaceURI` DOM property on those elements would, in fact, be `null` and **not** the 'inherited' default namespace.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/DOM-Parsing/issues/47#issuecomment-472137139