Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Invalid
-
Affects Version/s: 2.0.0
-
Fix Version/s: 2.0.1
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ace-showcase
Description
http://localhost:8080/ace-showcase/sliderEntry.jsf
The horizontal slider does respond to arrow keys, but the vertical one, right below it, does not, when the max value is set to 1000.
The horizontal slider does respond to arrow keys, but the vertical one, right below it, does not, when the max value is set to 1000.
Activity
Mark Collette
created issue -
Mark Collette
made changes -
Field | Original Value | New Value |
---|---|---|
Summary | vertical sliderEntry does respond to arrow keys | vertical sliderEntry does not respond to arrow keys |
Salesforce Case | [] |
Ken Fyten
made changes -
Salesforce Case | [] | |
Fix Version/s | 2.0.1 [ 10255 ] | |
Assignee Priority | P1 | |
Assignee | Mark Collette [ mark.collette ] |
Mark Collette
made changes -
Salesforce Case | [] | |
Description |
http://localhost:8080/ace-showcase/sliderEntry.jsf The horizontal slider does respond to arrow keys, but the vertical one, right below it, does not. |
http://localhost:8080/ace-showcase/sliderEntry.jsf The horizontal slider does respond to arrow keys, but the vertical one, right below it, does not, when the max value is set to 1000. |
Mark Collette
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Invalid [ 6 ] |
Ken Fyten
made changes -
Assignee Priority | P1 |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
The YUI slider does not internally store the exact value, as one might programmatically set on it. Instead it's designed to respond to user clicks, and so internally does calculations to resolve the value from the pixel location. So, if the range is greater than the pixel length of the slider, then the value ends up being a lossy conversion of value -> pixel -> calculated value. So when stepping by a fixed step value, you won't end up with the exact value you'd expect. If the range is grossly greater than the length, than the conversion rounding leads to the key presses doing nothing at all.
So, it's an application error to have a range (which is the max minus the min), that is sufficiently greater that the length. That will mean that a large swath of valus map to a single pixel point. If that swath of values is greater than the stepping pixel amount, then the step can't get to the next pixel, and will be unresponsive. You can overcome this by having a large enough stepPercent.
This is documented in the length and stepPercent properties on sliderEntry, as part of
ICE-6337.