-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
noUiSlider v11.1.0 does not work with current CSS !!! #31
Comments
@artknight Thanks for submitting this and sorry for the huge delay in my response. I'll check and see what other changes and additions are in the latest version of noUiSlider and see if we can accommodate the fix and improvements for the next patch. 😄 |
@hisk any idea when this might be released? |
@artknight Expect the next patch (which includes the fix for this issue) to be released in the next few days, at the latest by Monday. |
* Fix `$popover-arrow-width` interpolation issue #32. * Update package dependencies. * Add support for nouislider 11.1.0 - #31 * Update readme. * Fix demo page responsive display issues #29 * Update dependencies and bump version number. * Update distributed files. * Fix readme description. * Update changelog.
@artknight This issue was fixed in #33 |
@hisk Thank you for the fix!!! I just double-checked and it indeed works! I had to make one change though in _custom-slider.scss on line 17
...otherwise the handles were not aligned correctly. |
@artknight You are right, It should be |
* Fix `$popover-arrow-width` interpolation issue #32. * Update package dependencies. * Add support for nouislider 11.1.0 - #31 * Update readme. * Fix demo page responsive display issues #29 * Update dependencies and bump version number. * Update distributed files. * Fix readme description. * Update changelog.
I have upgraded our noUiSlider to the latest version ( 11.1.0 ) and shards-ui CSS breaks the slider. We are forced to resort to the native noUiSlider CSS. Please fix this.
Here is the screenshot of what happens
The text was updated successfully, but these errors were encountered: