Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.0
-
Fix Version/s: 2.0.1
-
Component/s: ACE-Components
-
Labels:None
-
Environment:IF 2, Adv. Comps
-
Assignee Priority:P1
Description
When using the ace-showcase, sliderEntry demo, if you change the value range to "0-10" instead of "0-100", then try to use the keyboard to adjust the value, you will notice that the keyboard step value doesn't get recalculated, so each step is still 5 units, instead of being adjusted to 1 unit per step, or whatever is appropriate for the value range.
The keyboard stepping range needs to be calculated whenever the value range is updated.
Also, the vertical sliderEntry it is not possible to navigate to 0 or 100, just 3 and 97, using the keyboard for some reason.
The keyboard stepping range needs to be calculated whenever the value range is updated.
Also, the vertical sliderEntry it is not possible to navigate to 0 or 100, just 3 and 97, using the keyboard for some reason.
Added stepPercent property to sliderEntry component, which has a default value of 10%. The idea being that, instead of specifying a fixed step value, or worse yet keeping the old hard-coded value of 5, the stepping will now automatically adjust to the range (max-min), and be a percent of it. Also, now it will go through the full range, and not get stuck just before the end.
The challenges in solving this were:
1. The component was caching a stale min and max value, so was not adapting to them changing. Addressed in
ICE-6530.2. Due to how YUI internally represents the slider value, it exacerbates application errors of misconfiguring the range with the length and the stepPercent. This is addressed in
ICE-6532.Adding the functionality to the component:
trunk
Subversion 23939
Subversion 23941
Modifying ace-showcase to demonstrate the functionality:
trunk
Subversion 23940