13917 2011-08-26 12:36:38 +0000 [create an element for a token] Should use getAttribute/setAttribute or define order of attributes manually. 2011-10-24 18:15:43 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#creating-and-inserting-elements P3 normal --- 1 contributor ian annevk bzbarsky hsivonen ian jackalmage mike Ms2ger public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 55852 0 contributor 2011-08-26 12:36:38 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/tokenization.html Multipage: http://www.whatwg.org/C#creating-and-inserting-elements Complete: http://www.whatwg.org/c#creating-and-inserting-elements Comment: [create an element for a token] Should use getAttribute/setAttribute or define order of attributes manually. Posted from: 91.181.110.19 by ms2ger@gmail.com User agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/534.35 (KHTML, like Gecko) Chrome/13.0.761.0 Safari/534.35 55869 1 jackalmage 2011-08-26 14:38:28 +0000 When an element is being created from markup the attributes are added all at once. 55873 2 Ms2ger 2011-08-26 14:59:04 +0000 Yes, but in what order? The spec needs to define the order of the attributes in element.attributes. 55877 3 jackalmage 2011-08-26 15:22:05 +0000 Ah, indeed. Agreed, then. (And obviously it should be source-order.) 56101 4 hsivonen 2011-08-31 12:56:52 +0000 (In reply to comment #3) > (And obviously it should be source-order.) "Obviously"? On the Web? See http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1125 in Firefox or IE. It's not clear to me that requiring a particular order is necessary or has positive effects that outweigh negative effects. 58145 5 ian 2011-10-12 19:37:00 +0000 Hm, yeah. Having the order exposed anywhere is unfortunate, but I guess it is exposed in the DOM since you can enumerate them... Maybe the enumeration should have a fixed order (alphabetical?) or some such? Seems bad to make the parser have to track order, and it seems bad that UAs would have to keep track of the order (since for some elements, UAs might want to store certain attribute values in custom ways rather than keeping them in an ordered map with all the other attributes). 58150 6 annevk 2011-10-12 20:17:35 +0000 Order is exposed in the DOM and in serialization. Alphabetical order is not compatible with anyone, but then I do not really care strongly here. 58769 7 ian 2011-10-24 18:15:43 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: I think we should fix this at the points where it can be observed, if at all, not at the points where the attributes are added. In principle, attributes are unordered, and it's only an artefact of the APIs that let you read the attributes that let you observe an order at all.