-
-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
Swiper Infinite loop scroll jumping #7270
Comments
Yeah I can see it |
I have same issue, only happens when using navigation to go from last to first then i clicking on any pagination in between and it jumps like crazy. Any help would be appriciated |
Same here, I have the similar error :( |
I wrote a quick fix to this issue, after dealing with it on production. For reference, my swiper configuration:
I really wanted a
This will eliminate the issue of the realIndex jumping like crazy when going backwards. If your issue appears when going forward on the slide, swap the functions. |
how can i fix it with react? |
still an issue today. Tried to implement this with solution proposed in thread @and-t, but couldn't produce the desired fix :( (I'm also using React) |
Check that this is really a bug
Reproduction link
https://codesandbox.io/p/sandbox/yl6ddq
Bug description
As an example, I will use the Slider Infinite Loop demo with 9 slides: https://swiperjs.com/demos/200-infinite-loop/core.
When you press the back button arrow to go from the first slide to the last slide and then press pagination dot to go from slide 9 to slide 8, you will notice a crazy jump through multiple slides, and it keeps happening when you switch between slides 8 and 9 using pagination dots.
Expected Behavior
Slider should scroll one slide
Actual Behavior
It scrolls multiple slides
https://github.com/nolimits4web/swiper/assets/48391144/0392a2c5-9847-44dd-9076-e4aed34486f5
Swiper version
v11.0.5
Platform/Target and Browser Versions
Windows /Linux Version 120.0.6099.111 (Official Build) (64-bit)
Validations
Would you like to open a PR for this bug?
The text was updated successfully, but these errors were encountered: