-
-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
Unexpected behavior when right clicking on a link #5625
Comments
Can confirm, same happening to me. If the slide is not on the first position, the right click will move that slide to the first position. |
Same happening here. Only seems to happen when slidesPerGroup is a different number to slidesPerView. |
Same behavior on smartphones after touch. That is, it is impossible to follow the link if it is inside the slide. Almost 2 months have passed, but this bug has not been fixed. Am I the only one who cares about the fact that it is impossible to use links inside slides. |
Hello, i got the same issue. |
Thanks |
Yes but I noticed it's CPU intensive. My sliders become laggy so I hope there's a better solution. I'm using version 8.3.2. |
This is now fixed for desktop but this is still an issue on mobile/touch devices in version 8.4.2 |
I have a solution that mobile touch on ui elements like links or select fields no longer makes the slide jump to first place. Touch events also trigger a focus event. I added a condition to check that the focus event was not triggered by touch. |
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. |
Check that this is really a bug
Reproduction link
https://swiperjs.com/demos#slides-per-view
Bug description
Right-clicking on a link in a slide will move to the next slide. To reproduce the error, the slide must not be the first in a row.
Expected Behavior
Context menu open
Actual Behavior
Move to the next slide and context menu open
Swiper version
8.1.0
Platform/Target and Browser Versions
Windows 10, Chrome
Validations
Would you like to open a PR for this bug?
The text was updated successfully, but these errors were encountered: