[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
Tue Nov 16 22:35:49 PST 2010


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





--- Comment #23 from Dai Mikurube <dmikurube at google.com>  2010-11-16 22:35:49 PST ---
(In reply to comment #22)

Ok. The top one and bottom one are strongly related. In summary :

> * "Natural" behavior
> The specification doesn't ask so, and Opera doesn't work so.  We shouldn't apply such behavior to stepUp() and stepDown() API.
> On the other hand, UI should work so.  It should be handled in Bug 45491.

For this,

- remove already existing behaviors (before my patch) on stepwise adjustment for JS API
  => It is included in fixing this bug.
- add (or fix) stepwise adjustment for UI
  => It should be done in Bug 45491.


> * 0.00392156863 * 255 rounding
> This is also out of scope of this bug.  We had better make another bug entry.

I agree. I found we can calculate it if just using IEEE 754 single precision numbers.
We should re-consider precisions and how to print them in another bug.



> * stepUp()/stepDown() behavior with step-mismatching values
> We should focus on it in this bug.
> IMO, we should follow the specification, not Opera.  Opera might change its behavior in the future.

Ok, this is, actually, removing stepwise adjustment for JS API.
So the latest patch is near to the specification except for UI changes in stepUpFromRenderer().
(UI changes should be done in Bug 45491.)

-- 
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