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
When multiple swipers have been initialised on the page and the window is resized by the user, only one of the swipers will continue autoplaying, the rest of the swipers will be set to a paused state.
They can be resumed with .autoplay.resume() successfully, but they should not need this in the first place as the swiper was never paused.
Expected Behavior
All swipers on the page continue to autoplay after the browser window has been resized
Actual Behavior
Only the most recently initialized swiper will continue to autoplay, and any other swiper will pause itself.
Swiper version
9.2.2
Platform/Target and Browser Versions
All (Tested on Windows 10 and Ubuntu 22.04.2 -> Chrome 111.0.x)
Any quick workarounds on how to fix it? Tried a combination of resize event listeners, initialize/destroy the slider, etc. and nothing seems to work.
Additionally, after the slider completes a cycle it will just stop. Which is an ever bigger problem because people won't ever get to see the content outside the viewport once it does.
Check that this is really a bug
Reproduction link
https://codepen.io/zmcwilliam/pen/abRZzJp
Bug description
When multiple swipers have been initialised on the page and the window is resized by the user, only one of the swipers will continue autoplaying, the rest of the swipers will be set to a paused state.
They can be resumed with .autoplay.resume() successfully, but they should not need this in the first place as the swiper was never paused.
Expected Behavior
All swipers on the page continue to autoplay after the browser window has been resized
Actual Behavior
Only the most recently initialized swiper will continue to autoplay, and any other swiper will pause itself.
Swiper version
9.2.2
Platform/Target and Browser Versions
All (Tested on Windows 10 and Ubuntu 22.04.2 -> Chrome 111.0.x)
Validations
Would you like to open a PR for this bug?
The text was updated successfully, but these errors were encountered: