- From: <bugzilla@jessica.w3.org>
- Date: Mon, 08 Oct 2012 19:27:59 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17871 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |www-dom@w3.org Component|HTML |DOM AssignedTo|ian@hixie.ch |annevk@annevk.nl Product|WHATWG |WebAppsWG Summary|Element attributes should |Element attributes should |not be required to be |not be required to be |stored in an ordered list, |stored in an ordered list |.innerHTML remains | |unspecified | QAContact|contributor@whatwg.org |public-webapps-bugzilla@w3. | |org --- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch> 2012-10-08 19:27:58 UTC --- I don't think using innerHTML in tests is sane. So I wouldn't recommend doing that. The order of attributes in valid HTML markup is not meaningful, and so you should not be comparing HTML markup for equality by string comparison, since you will have false negatives. It's like comparing numbers for equality by string comparison; you'll miss cases like "01" and "1.0" being the same number. As Henri says, browsers don't keep a predictable order, so we're not required to expose one by compatibility; and in fact they get some good performance optimisations from not doing so, so I don't think it's a good idea to require a predictable order. Stable order, sure, but not predictable. So I think this is a bug in DOM Core. -- 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 Monday, 8 October 2012 19:28:00 UTC