554016 - setAttributeNS("unknown", "align") after setAttributeNS(null, "align") changes return value of getAttribute("align")

Status: NEW

(Core :: DOM: Core & HTML, defect, P5)

Description

[:Gavin Sharp [email: [e-mail]]]

I don't know what the justification is for this test's expected results ("DOM L2 Core" is all that's listed), but apparently we're the only browser that fails it:

http://samples.msdn.microsoft.com/ietestcenter/#domcore

Comment 1

[:Ms2ger (he/him; ⌚ UTC+1/+2)]

This only happens for "mapped attributes". DOM 2 Core doesn't actually define the correct behavior here.

Comment 2

[Alex Vincent [:WeirdAl]]

The second attribute of setAttributeNS (or createElementNS, for that matter) is a qualified name - prefix plus local name.

DOM 3 Core backs us up on this.
http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/core.html#ID-ElSetAttrNS

Comment 3

[Alex Vincent [:WeirdAl]]

Oh, I see... it's because they're using getAttribute() (DOM Level 1) with setAttributeNS() (DOM Level 2).  The getAttribute() method isn't particularly well suited to work with setAttributeNS, because the latter uses namespaces, and the former doesn't.

"Calling Element.getAttribute(name)  with that nodeName could then return any of those attributes. The result depends on the implementation."
http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/core.html#Namespaces-Considerations

Comment 4

[Boris Zbarsky [:bzbarsky]]

Yeah, this test is bogus, imo.  At least pending some sort of errata to the DOM specs defining the behavior.

Comment 5

[d]

So, if the conclusion is that the test is invalid, we should ask Microsoft to remove it, right?

Comment 6

[Olli Pettay [:smaug][[e-mail]]]

I sent an email to my MS contact.

Comment 7

[Boris Zbarsky [:bzbarsky]]

What this test is _actually_ testing is that a certain ordering is imposed on attributes with the same localname but different namespace URIs (at least in terms of the lookup order for getAttribute).  The DOM does not guarantee such an ordering.  So yes, we should ask Microsoft to remove the test.

Comment 8

[Olli Pettay [:smaug][[e-mail]]]

I did send this information to Travis, and he promised to forward it to whoever
maintains that page.

Comment 9

[d]

It's still there... but of course that is expected. Every second of showing a faulty score to our disadvantage makes IE9 seem better.

Comment 10

[Olli Pettay [:smaug][[e-mail]]]

That is unfortunate indeed, but what can we do if MS decides to put invalid
testcase to their web page, and not react too fast to comments to fix the pages.

Comment 11

[Anne (:annevk)]

The current DOM specification does impose some kind of ordering for what it's worth. setAttribute/setAttributeNS calls append attributes to an ordered list.

Comment 12

[Firefox Bug Husbandry Bot]

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

Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.