-
-
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
Search for the custom navigation control buttons in the swiper-container #7714
Comments
Ashkanph
added a commit
to Ashkanph/swiper
that referenced
this issue
Sep 2, 2024
Is the following change acceptable to the maintainers as a solution? |
Yes, PR is welcome |
nolimits4web
pushed a commit
that referenced
this issue
Sep 2, 2024
Fixed by #7716 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Check that this is really a bug
Reproduction link
https://codesandbox.io/p/sandbox/sn7mfn
Bug description
If there are more than one Swiper custom element with custom navigation buttons (for example in the
container-end
slot), if they use the same CSS selectors for their navigation buttons, clicking on one of the buttons swipes both sliders.This can be solved by using different CSS selectors for the buttons, but in version 9 there was no need to have different CSS selectors; because the custom buttons were part of
swiper.el
, but in versions >= 10 the custom buttons are no longer descendants ofswiper.el
, they are descendants ofswiper.hostEl
.Expected Behavior
There is no need to have different CSS selectors for the custom navigation buttons of the Swiper custom elements on a page.
Actual Behavior
No response
Swiper version
11.1.12
Platform/Target and Browser Versions
All of the platforms
Validations
Would you like to open a PR for this bug?
The text was updated successfully, but these errors were encountered: