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
I have searched the issues of this repository and believe that this is not a duplicate.
What problem does this feature solve?
In case of horizontal slider while the user is using the slider the marks gets hidden below the cursor. This can create confusion in some cases. This can be solved by having marks above the slider.
Similarly, In case of vertical slider there might be some use case to have slider on the left side of the line. However as per the current API there is no may to change the position of marker in horizontal it is always on the bottom in vertical slider it is always on the right side
What does the proposed API look like?
Slider component should have a props to allow markers to be on the other side of the line
This can be achieved the in the following way
Using type marksPosition = 'left' | 'right' | 'above' | 'below', right, left only work in case of vertical slider and above below for horizontal marker
Using a boolean flag alternateMarkPosition true will move marker to alternate position
The text was updated successfully, but these errors were encountered:
What problem does this feature solve?
In case of horizontal slider while the user is using the slider the marks gets hidden below the cursor. This can create confusion in some cases. This can be solved by having marks above the slider.
Similarly, In case of vertical slider there might be some use case to have slider on the left side of the line. However as per the current API there is no may to change the position of marker in horizontal it is always on the bottom in vertical slider it is always on the right side
What does the proposed API look like?
Slider component should have a props to allow markers to be on the other side of the line
This can be achieved the in the following way
The text was updated successfully, but these errors were encountered: