[Webkit-unassigned] [Bug 36259] New: <input type=range> does not validate correctly without a renderer and the tests are incorrect

[bugzilla-daemon at webkit.org]

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

           Summary: <input type=range> does not validate correctly without
                    a renderer and the tests are incorrect
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: Mac OS X 10.5
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: HTML DOM
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: joepeck at webkit.org


Created an attachment (id=50984)
 --> (https://bugs.webkit.org/attachment.cgi?id=50984)
[TEST] - Shows Unexpected <input type=range> Behavior

The HTML5 Specification currently states:
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html

For underflow (and likewise for overflow) part of the value sanitization
algorithm:

> [[ When the element is suffering from an underflow, the user agent must set the
>   element's value to a valid floating point number that represents the minimum. ]]

I got clarification from Hixie that the range input, when stable, should never
be
in the underflow / overflow state. IRC Log:

> Hixie: it can momentarily suffer from an underflow if you use script to set it
> to a value below the minimum. But that sentence means the steady state can't
> suffer from an underflow. if that makes sense

The spec says to run the "value sanitization algorithm" when (paraphrased):
  - an input element's type attribute changes state
  - when the element is first created
  - when the value content attribute is added, set, or removed

Some of the current tests in the tree do not exhibit correct behavior, and also
are providing incorrect values as expected values. To name a few:

  LayoutTests/fast/forms/ValidityState-rangeOverflow-range.html
  LayoutTests/fast/forms/ValidityState-rangeUnderflow-range.html

I believe just a little refactoring of code is needed. Informal test attached,
view the source to see expected values.

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