[Bug 17176] Element attributes should not be required to be stored in an ordered list, .innerHTML remains unspecified

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

--- Comment #1 from Divye <divye_kapoor@hotmail.com> 2012-05-25 08:22:36 UTC ---
The super short summary of the bug is:
1) There's a mistake in the spec by requiring that Element.attributes be an
ordered list instead of just an indexable list since the ordering function is
undefined.
2) The fact that we're now trying to use an unordered Element.attributes during
serialization poses difficulties in reliably comparing for equality the
.innerHTML of 2 identical DOMFragments in different parts of the DOM of the
page since the rendered strings will not match because even the same tags and
attributes can be rendered into different .innerHTML strings based on how they
ended up being constructed (page load time or through JS etc.).

(2) is a problem for testing because there doesn't seem to be a way to
"standardize" HTML even within the same browser and prevents the development of
a cross browser assertHTMLEquals function where one of the arguments is a well
defined "expected" string because a DOM dump from Chrome and FF yield strings
that differ in attribute ordering for identical DOM structures constructed in
different manners (eg. 2 DOMElements one constructed at Page load or through JS
attribute modifications, other through .innerHTML = string yield different
.innerHTML even on the same browser).

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Friday, 25 May 2012 08:22:40 UTC