Skip to content
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

Auto slides in conjunction with loop causes all sorts of issues #7787

Open
5 of 6 tasks
arl1nd opened this issue Nov 7, 2024 · 0 comments
Open
5 of 6 tasks

Auto slides in conjunction with loop causes all sorts of issues #7787

arl1nd opened this issue Nov 7, 2024 · 0 comments

Comments

@arl1nd
Copy link

arl1nd commented Nov 7, 2024

Check that this is really a bug

  • I confirm

Reproduction link

https://codepen.io/arl1nd/pen/QWeZmdr?editors=1100

Bug description

Hello,

I have a straightforward setup that causes an unusual issue with Swiper. Although I've reviewed similar reported issues, this case includes additional properties that seem to disrupt the slider functionality. In the reproduction link, you can see that adding:

loop: true,
slidesPerView: 'auto',

Causes weird behavior of the Swiper slider, even though the loop option is enabled, it won't loop to the slides.

To make things ever worse, adding centeredSlides: true sets the last slide as first!

So I thought, adding more slides via loopAdditionalSlides: {number} could fix this, but it made things even worse.

I believe that you should reconsider the implementation on this crucial part, as it clearly has issues in it.

Otherwise, Swiper is the way to go, so thank you for maintaining such a wonderful library.

Arlind

Expected Behavior

No response

Actual Behavior

No response

Swiper version

11.1.14

Platform/Target and Browser Versions

macOS Sequioa Chrome 131

Validations

  • Follow our Code of Conduct
  • Read the docs.
  • Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
  • Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

  • I'm willing to open a PR
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant