[Bug 17871] Element attributes should not be required to be stored in an ordered list

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17871

--- Comment #8 from Boris Zbarsky <bzbarsky@mit.edu> ---
Changing the attribute order setup in Gecko would probably have unacceptable
performance implications unless we completely rearchitect how we do
presentational hints.  I don't believe we have any plans of doing either one of
these things in any measurable timeframe.

So no, I guess I'm not OK with it.  ;)

As for setAttribute, say, depending on attribute order, that only matters if
you have two attributes already set that have the same "name", right?  Since
Gecko only changes the order for preshints, it only does so for names that do
not contain a ':'.  Does setAttributeNS actually allow you to set an attribute
with a non-null namespace but a name that doesn't contain ':'?  That's the only
way there could possibly be a problem here.  And even then you'd have to have
someone actually doing that, on an HTML element, with a localName that matches
a preshint name.  Which no one does in practice, quite honestly.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 13 December 2012 16:00:00 UTC