-
-
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 loopAdditionalSlides prop not working #7492
Comments
t0ggles-create Swiper |
Task nolimits4web/SWIPER-93 was created |
I have the same question. |
any news? loopAdditionalSlides and loopAddBlankSlides not working |
Confirming on the latest v11.1.4 loopAddBlankSlides and loopAdditionalSlides props are not working. |
I have the same question, the current solution is to roll back the version to v10.3.1, |
Any news from this issue? |
I met the same problem in React. |
same problem with loopAdditionalSlides prop.... |
I have same problem |
I have same problem in Vue3 |
sampe problem too |
+1 |
Not working for me |
I also have the same problem |
Same here |
same here |
Is there any workaround in the meantime ? |
Still an issue in the latest version 11.2.4. Had to downgrade all the way to version 8.4.7 to get a working instance of loopAdditionalSlides. |
+1 - working with 10.3.1 |
Check that this is really a bug
Reproduction link
https://codesandbox.io/p/devbox/swiper11-loop-centeredslides-ypzfmn?file=%2Fsrc%2FApp.vue%3A12%2C6-12%2C26
Bug description
I noticed that although I've set loopAdditionalSlides on CodeSandbox, it doesn't seem to have any effect. Upon inspecting the elements in devtools, I found that loopAdditionalSlides is being passed as an attribute. Upon further investigation of the source code, I realized that loopAdditionalSlides prop is not defined.
Expected Behavior
loopAdditionalSlides should be passed as props
Actual Behavior
loopAdditionalSlides not working
Swiper version
11.1.1
Platform/Target and Browser Versions
Windows/124.0.6367.61 (正式版本) (64 位元)
Validations
Would you like to open a PR for this bug?
The text was updated successfully, but these errors were encountered: