[Webkit-unassigned] [Bug 36259] <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


TAMURA, Kent <tkent at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tkent at chromium.org




--- Comment #6 from TAMURA, Kent <tkent at chromium.org>  2010-03-17 19:28:24 PST ---
(In reply to comment #5)
> Yes, I am going to start using StepRange inside HTMLInputElement to validate
> <input type=range> values instead of with the renderer. I guess this could have
> gone directly into HTMLInputElement, but I figured it would be generic and more
> manageable as a separate file. I may make small changes to the  StepRange
> struct which are much easier to notice in a separate patch instead of at the
> same time as a move.

Ok.  So we'll have just one more patch?

> Kent TAMURA, I see you have done a lot with validation in the past. Would you
> agree that with the current spec rangeOverflow, rangeUnderflow, and
> stepMismatch should never be true with an <input type=range>? That seems to be
> where I am heading (removing the range specific tests completely). The spec has
> a lot of "must"s which are "may" in the date / time inputs you worked on.

Yes, I agree with it.

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