[Webkit-unassigned] [Bug 48976] stepUp/stepDown for values in step-mismatching state for input elements

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Nov 15 21:19:58 PST 2010


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





--- Comment #8 from Dai Mikurube <dmikurube at google.com>  2010-11-15 21:19:58 PST ---
(In reply to comment #7)
> (In reply to comment #6)
> > (In reply to comment #5)
> > Thank you, Kent-san.
> > 
> > I see. To follow the spec, the current implementation (without my patch) should be changed so that :
> > 
> > 1. <input type="number" step="1" min="0" max="9.9" value="8.7" />
> > 2. stepUp() => 9.7
> > 
> > Though it looks a little unnatural... Are there any other opinions from someone else?
> 
> stepUp()/stepDown(), which are JavaScript API, should follow the specification, and I think a page author have the responsibility of validity of the resultant values.
> 
> The behavior of HTMLInputElement::stepUpFromRenderer(), which is the function called by spin-button click, should be "natural".

Ok,
- I removed any stepwise adjustment for stepUp()/stepDown(). (removing numerical errors is alive.)
- I added stepwise adjustment for stepUpFromRenderer() with "natural" behaviors for step-mismatched values.

Then, do you have any ideas to test stepUpFromRenderer()? I guess that sending an event (e.g. key up/down) will work, but a simpler way may be better.

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



More information about the webkit-unassigned mailing list