-
-
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
centerInsufficientSlides doesn't count slidesOffsetBefore/slidesOffsetAfter params #5436
Comments
Would love for this to be implemented! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I'm bumping into this issue as well. I think this could be solved by not applying the slidesOffsetBefore & slidesOffsetAfter when the centerInsufficientSlides gets triggered or better yet by subtracting the offset from the x value in the translate3D function. |
I am facing same problem even with equal offset before and after it doesnt center correctly. In the end what I did was add left padding in first .swiper-slide and right padding to last .swiper-slide div. |
I have the same problem |
When using any SlidesOffset the wrapper gets position wrong (translate3D xpos is double/triple what it should be) |
Issue is closed because of outdated/irrelevant/not actual/needed more information/inactivity. If this issue is still actual and reproducible for latest version of Swiper, please create new issue and fill the issue template correctly:
|
Check that this is really a bug
Reproduction link
see attached screenshot from file updateSlides.js
Bug description
centerInsufficientSlides
doesn't countslidesOffsetBefore/slidesOffsetAfter
paramsAs a result slides NOT CENTERED correctly.
When I remove slidesOffset params - it centers correctly.
Please fix it.
Expected Behavior
No response
Actual Behavior
No response
Swiper version
8.0.3
Platform/Target and Browser Versions
all
Validations
Would you like to open a PR for this bug?
The text was updated successfully, but these errors were encountered: