Search and Top Navigation
#8965 closed bug (notabug)
Opened January 16, 2013 01:55AM UTC
Closed January 16, 2013 02:08AM UTC
Spinner Control Stepping Issue
Reported by: | tleduc@bptrade.com | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | none |
Component: | ui.spinner | Version: | 1.9.2 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
I have ran into a couple issues with the spinner control where the stepping doesn't seem to be working as anticipated.
If you have a min value other than 0, it gets added to the step.
{step:10,min:03}
value = 50
step up: new value 63, expected 60
step down: new value 43, expected 40
The other issue is double stepping
{step:10,min:0,max:1000}
value = 101
step up: new value 110, expected 110
step down: new value 90, expected 100
value = 105
step up: new value 120, expected 110
step down: new value 10, expected 10
examples: http://jsfiddle.net/MWuf2/3/
Attachments (0)
Change History (1)
Changed January 16, 2013 02:08AM UTC by comment:1
_comment0: | None of these are bugs. The values are changes, then clamped. The steps start at the min. → 1358302175809647 |
---|---|
resolution: | → notabug |
status: | new → closed |
None of these are bugs. The values are changed, then clamped. The steps start at the min.