58281 2011-04-11 15:52:21 -0700 Order of 'max' and 'value' attributes of <input type=range> matters in XHTML (and one order is broken) 2011-06-16 17:34:48 -0700 1 1 1 Unclassified WebKit Forms 528+ (Nightly build) PC OS X 10.5 RESOLVED FIXED P2 Normal --- 1 ian webkit-unassigned ap dglazkov keishi tkent oldest_to_newest 383618 0 ian 2011-04-11 15:52:21 -0700 In XHTML, these result in different behaviour: <input type="range" max="100" value="10"/> <input type="range" value="10" max="100"/> There are two problems here: 1. The order of setting these attributes shouldn't matter. Even if they are set from script one after the other, the algorithms in the spec should ensure the result is the same. 2. The attributes of an element created by a parser should all be set simultaneously when the element is created, not one at a time. So there should never be a situation in which you can tell in which order the attributes were set. 422349 1 tkent 2011-06-16 17:34:48 -0700 I think this was fixed by http://trac.webkit.org/changeset/89006 However, I don't understand why this happened only in XHTML :-)