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
Not sure how to word this (videos below), but essentially our slider input can only be dragged in a small portion of the displayed slider. The range/steps are the same as expected, but for some reason don't take up the full width of the component.
Any ideas what could have changed this behavior and/or what I can do to fix it?
Didn't provide any implementation details because we're quite literally just passing standard options (min, max, step, start, etc) to noUiSlider.create. Other components are just aligned properly to make it look fancy on top. We copy/pasted the default styles at some point (and are overriding separately as necessary), but it doesn't look like those have changed.
The text was updated successfully, but these errors were encountered:
Yeah, this is unfortunate; I'm sorry you ran into this issue. #1167 is open with some more discussion on this. I'll update the release notes to make this clearer.
Not sure how to word this (videos below), but essentially our slider input can only be dragged in a small portion of the displayed slider. The range/steps are the same as expected, but for some reason don't take up the full width of the component.
Works as intended in 15.4:
https://user-images.githubusercontent.com/44090970/181095668-7da03df5-5ae0-4fb1-9020-bad55512e8a0.mov
Behavior seen in 15.5 or greater:
https://user-images.githubusercontent.com/44090970/181095679-aeb37932-39a1-452b-ad50-275297268672.mov
Any ideas what could have changed this behavior and/or what I can do to fix it?
Didn't provide any implementation details because we're quite literally just passing standard options (min, max, step, start, etc) to noUiSlider.create. Other components are just aligned properly to make it look fancy on top. We copy/pasted the default styles at some point (and are overriding separately as necessary), but it doesn't look like those have changed.
The text was updated successfully, but these errors were encountered: