You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we can only set the increment like 0, 5, 10, 15, 20, 25, 30.
We have use case where we need to set up 1, 5, 10, 15, 20, 30
So from current implementation we want to start with 1 instead of 0, and omit the 25 value.
Also we need the "marks" to give the user information which values are allowed
Expected slider option below
The solution
Option to specify the list of possible values with labels which will be used to display marks
Solution has to support keyboard navigation
Thank you for submitting a feature request. Your proposal is open and will soon be triaged by the Carbon team.
If your proposal is accepted and the Carbon team has bandwidth they will take on the issue, or else request you or other volunteers from the community to work on this issue.
Hi @parejko! The step prop already allows increments and you can customize javascript to remove steps. The min prop will allow you to set the start value to 1,
Enhancement opportunity
The increment visuals (tick marks + value) are not currently part of the component and would need to be added as an enhancement.
Maintainer note: There have been other issues related to this topic in the past, we should find those.
The problem
Currently we can only set the increment like 0, 5, 10, 15, 20, 25, 30.
We have use case where we need to set up 1, 5, 10, 15, 20, 30
So from current implementation we want to start with 1 instead of 0, and omit the 25 value.
Also we need the "marks" to give the user information which values are allowed
Expected slider option below
The solution
Option to specify the list of possible values with labels which will be used to display marks
Solution has to support keyboard navigation
Examples
No response
Application/PAL
Instana
Business priority
None
Available extra resources
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: