Limited availability during the holidays
Another busy year is coming to its end, and an exciting year lies ahead. In order to get ready for a fresh new start, our team will spend a few days' rest during the winter holidays. Over the holiday break, we will have reduced staffing from December 20th, 2025, to January 4th, 2026, so please be patient if you do not receive a response as quickly as you normally would.
We send our warmest wishes for happiness, health, and success throughout the coming year. Thank you for your continued support, and may you have a peaceful and blessed Happy Holidays!
Hello, when this option is enabled and the page scroll position is changed (via hash(#) navigation or a jump to top script) the page immediately jumps back to the slider position when scrolled again afterwards.
Is there a possibility to prevent this behavior and reset the slider so it only is played again when scrolled into view manually.
Hello Sascha Schürmann,
Could you please show us your site or a test page with the slider where we can check on this to investigate ?
Hi Attila,
it's even the case in the demo:
https://layerslider.kreaturamedia.com/sliders/play-by-scroll/
When you scrolled a few slides via mouse wheel and use the scrollbar to scroll the page to top or bottom and use the mousewheel afterwards again, the page is immediately scrolled to the last slider position.
This is the case in IE, FF and Chrome.
It might be a feature but it's not the behaviour I would expect when I'm scrolling a web page.
I just want everything resetted when I leave the slideshow via scrollbar or a jump to a hash
I tried to kill the slider - which worked, but I didn't find a method in the api to reinstance it again.
It is not a bug, this is how the play by scroll effect is working currently. Basically, until the slider is "in action" (not played through forward or backwards), the scrolling is blocked. Even if you skip to a different section of the page, once you start scrolling it will jump back to the slider.
We will consider changing this behavior in future updates, but at the moment this is how it works.
Thank you for your understanding and sorry for any inconvenience.