[Webkit-unassigned] [Bug 58281] New: Order of 'max' and 'value' attributes of <input type=range> matters in XHTML (and one order is broken)

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=58281

           Summary: Order of 'max' and 'value' attributes of <input
                    type=range> matters in XHTML (and one order is broken)
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Mac OS X 10.5
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Forms
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: ian at hixie.ch


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.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.