- From: <bugzilla@jessica.w3.org>
- Date: Tue, 29 May 2012 11:57:09 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17176
Henri Sivonen <hsivonen@iki.fi> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hsivonen@iki.fi
--- Comment #5 from Henri Sivonen <hsivonen@iki.fi> 2012-05-29 11:57:08 UTC ---
(In reply to comment #4)
> And for web compat, the order of the attributes created by the HTML parser
> needs to be the same as the order in the markup, right?
Web compatibility requires that when there are attributes with the same name
the first attribute of a given name wins. In addition, at least some older
versions of the NPAPI version of Flash Player required the order in which
attributes of the embed element are passed to the plug-in to match the source
order of attributes.
As far as I can tell, there isn't a good reason to believe that the iteration
order of attributes or the serialization order of attributes matters for Web
compatibility. After all, neither Trident nor Gecko preserves the order of
attributes. It appears that Trident shuffles all attributes according to the
implementation details of a hash function of some kind and Gecko doesn't
preserve the order of attributes that are legacy presentational hints relative
to attributes that are not legacy presentational hints.
--
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 Tuesday, 29 May 2012 11:57:16 UTC