Bug 58281
| Summary: | Order of 'max' and 'value' attributes of <input type=range> matters in XHTML (and one order is broken) | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ian 'Hixie' Hickson <ian> |
| Component: | Forms | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | ap, dglazkov, keishi, tkent |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | OS X 10.5 | ||
Ian 'Hixie' Hickson
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Kent Tamura
I think this was fixed by http://trac.webkit.org/changeset/89006
However, I don't understand why this happened only in XHTML :-)