Chrome Version: 59 canary
OS: All but iOS
What steps will reproduce the problem?
(1) Open http://w3c-test.org/dom/nodes/Node-lookupNamespaceURI.html
What is the expected result?
The following sub-tests pass:
- DocumentFragment is in default namespace, prefix null
- DocumentFragment is in default namespace, prefix ""
- Empty namespace is not default, prefix null
- Empty namespace is not default, prefix ""
What happens instead?
They fail.
Please use labels and text to provide additional information.
https://dom.spec.whatwg.org/#dom-node-isdefaultnamespace
The current implementation doesn't handle cases where the node has no parent and null namespace is specified correctly.
These tests pass with Firefox.
Comment 1 by bugdroid1@chromium.org
, Mar 10 2017