{"issue":{"created_at":"2011-12-13T22:31:28Z","state":"open","updated_at":"2011-12-14T01:42:55Z","user":{"gravatar_id":"ebdb5e5bbdcf2d0bf7aa06a7620cb525","id":212795,"url":"https://api.github.com/users/pyrtsa","avatar_url":"https://secure.gravatar.com/avatar/ebdb5e5bbdcf2d0bf7aa06a7620cb525?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"pyrtsa"},"comments":1,"body":"By the HTML spec, element attributes may appear in any order, but for some reason not apparent in its version history, Temple imposes the alphabetical ordering to them. I think it's pointless, makes comparing the abstract source vs. rendered output harder, and should thus be removed. (And, FWIW, this probably brings a negligible improvement to rendering times.)\r\n\r\nFor an example, in Slim notation,\r\n\r\n    meta(http-equiv=\"Content-Type\" content=\"text/html; charset=utf-8\")\r\n\r\nrenders nicer when the output is unsorted like:\r\n\r\n    <meta http-equiv=\"Content-Type\" content=\"text/html; charset=utf-8\" />\r\n\r\nrather than sorted like:\r\n\r\n    <meta content=\"text/html; charset=utf-8\" http-equiv=\"Content-Type\" />","assignee":null,"id":2544807,"number":52,"pull_request":{"patch_url":"https://github.com/judofyr/temple/pull/52.patch","html_url":"https://github.com/judofyr/temple/pull/52","diff_url":"https://github.com/judofyr/temple/pull/52.diff"},"labels":[],"title":"Keep HTML attributes in their original order","html_url":"https://github.com/judofyr/temple/issues/52","closed_at":null,"url":"https://api.github.com/repos/judofyr/temple/issues/52","milestone":null},"action":"created","comment":{"created_at":"2011-12-14T01:42:55Z","updated_at":"2011-12-14T01:42:55Z","user":{"gravatar_id":"a191f038556d3564e2a2b31deac38f60","id":6162,"url":"https://api.github.com/users/stonean","avatar_url":"https://secure.gravatar.com/avatar/a191f038556d3564e2a2b31deac38f60?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"stonean"},"body":"Actually, having the attributes ordered does have a point for me: testing. Due to the unordered nature of hashes (prior to Ruby 1.9) the resulting html attributes could be in any order, complicating testing. ","id":3134094,"url":"https://api.github.com/repos/judofyr/temple/issues/comments/3134094"}}