Slider - (re)define scope and prototype component(s) #437
Open
3 tasks
Labels
⭕ core team issue
This is for the core team and should not be done by contributors
🎨 design issue
Task is for designers
⌨️ dev issue
Task is for developers
Milestone
Description / User Story
With this task we want to (re)define the scope of the slider and prototype the component(s).
Currently there are 4 slider variants. We should check if we can reduce the amount of Slider components and combine existing variants. After this task should have at least 2 Slider components: a single value slider (named: SliderSingleValue) and a two value slider (named: SliderTwoValues). If possible we could reduce the amount even more to only have one Slider component that covers all variants. Currently there are also separate components named SliderSingleValueWithLegend and SliderTwoValuesWithLegend, which should not exist after this issue has been solved.
We should also define i.e. how the stepper behaviour should be for the multi-value slider. One option could be, that decreasing the higher value slider so much, that the values of both sliders are identical, a further decrease via the stepper buttons would decrease both slider values. Another option would be to disable the stepper buttons once the above described scenario happens, so that a higher value slider for example can not influence the lower value slider and vice-versa. Also the stepper buttons would be disabled when the sliders are already at the highest or the lowest value that is possible.
After this task is done, the decisions need to be integrated into design and code with #268 .
Acceptance Criteria
Background information
The text was updated successfully, but these errors were encountered: