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
{{ message }}
This repository has been archived by the owner on May 30, 2024. It is now read-only.
I am currently working on a project which initialises the rangeslider, then hides it (with display none), and then is animated back onto the screen. It appears if the dynamically created slider is hidden and resized, it causes the value to be lost / changed.
You can reproduce the issue by visiting the tester/demo site: rangeslider.js.org and opening inspect, setting the dynamically created rangeslider to "display: none;". Now, resize the screen and you'll see that the output will jump between the min and max. This is also true if you un-hide the native slider. The original value is lost.
To fix this ourselves (I am hosting v2.3.0) you can add this condition to the original resize function (which invokes the rangeslider update function):
Cheers.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi there,
I am currently working on a project which initialises the rangeslider, then hides it (with display none), and then is animated back onto the screen. It appears if the dynamically created slider is hidden and resized, it causes the value to be lost / changed.
You can reproduce the issue by visiting the tester/demo site: rangeslider.js.org and opening inspect, setting the dynamically created rangeslider to "display: none;". Now, resize the screen and you'll see that the output will jump between the min and max. This is also true if you un-hide the native slider. The original value is lost.
To fix this ourselves (I am hosting v2.3.0) you can add this condition to the original resize function (which invokes the rangeslider update function):
Cheers.
The text was updated successfully, but these errors were encountered: