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
Big thanks for the very useful component. I'm not an expert on HTML/CSS/JS, apologies if I'm not properly using the component.
I have a page with a horizontal and a vertical slider. Setup as on the examples:
sldHScroll = new Slider('#sldHScroll', {
orientation: 'horizontal',
handle: 'square'
});
sldVScroll = new Slider('#sldVScroll', {
orientation: 'vertical',
handle: 'square'
}
On my window.resize handler I try to set the width of the horizontal slider by setting style.width of #sldHScroll and the height of the vertical slider by setting style.height of #sldVScroll. The horizontal slider sets properly but the vertical slider height is always sets to 210 pixels regardless of my setting of style.height.
Editing bootstrap-slider.js solved the issue:
I added the following after line 450: var origHeight = this.element.style.height;
I added the following after line 680: this.sliderElem.style.height = origHeight;
Is there a different way to handle this use case?
Thanks,
Enrique
The text was updated successfully, but these errors were encountered:
Big thanks for the very useful component. I'm not an expert on HTML/CSS/JS, apologies if I'm not properly using the component.
I have a page with a horizontal and a vertical slider. Setup as on the examples:
sldHScroll = new Slider('#sldHScroll', {
orientation: 'horizontal',
handle: 'square'
});
sldVScroll = new Slider('#sldVScroll', {
orientation: 'vertical',
handle: 'square'
}
On my window.resize handler I try to set the width of the horizontal slider by setting style.width of #sldHScroll and the height of the vertical slider by setting style.height of #sldVScroll. The horizontal slider sets properly but the vertical slider height is always sets to 210 pixels regardless of my setting of style.height.
Editing bootstrap-slider.js solved the issue:
Is there a different way to handle this use case?
Thanks,
Enrique
The text was updated successfully, but these errors were encountered: