Closed saswatds closed 5 years ago
Noticed this too after an update. Removing $($elem).slimScroll({ destroy: true });
seems to resolve, however this has been in the code since the 2nd commit and is likely necessary. Still exploring this. Did you come to any conclusions yourself?
The underlying cause may be to do with slimscroll itself or elsewhere, but this is fixed by putting back a call to refresh()
that used to be at the top of init()
(now called registerWatch()
). You may also want to add noWatch
to your options as slimscroll might be being destroyed and reinstated several times.
Edit: Note that this 'fix' has other implications with slimscroll 1.3.7 as you'll get a double scrollbar. With 1.3.2 it's fine. Unsatisfactory but at least there is a working combo.
Is there a proper solution for this already? Walking into this issue as well.
Hi, Have you an issue for this . I call
[code]
<div class="scroll-body" slimscroll="{noWatch:true,railColor:'#FF69B4'}" style="height: 150px;">
[/code]
And nothing effect color to the scroolbar. Maybe I don't understood ?
The options which i put doesnt seem to take any effect on the slimscroll. The touch responsize is very bad too