-
-
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
IgnoredEventCancel : intervention: Ignored attempt to cancel a touchmove event with canclable=false #7415
Closed
6 tasks done
chonlatit-tpit opened this issue
Mar 25, 2024
· 6 comments
· Fixed by Mapuppy09/tradetrust-website#8 · 4 remaining pull requests
Closed
6 tasks done
IgnoredEventCancel : intervention: Ignored attempt to cancel a touchmove event with canclable=false #7415
chonlatit-tpit opened this issue
Mar 25, 2024
· 6 comments
· Fixed by Mapuppy09/tradetrust-website#8 · 4 remaining pull requests
Labels
t0ggles
Linked to the t0ggles task
Comments
t0ggles-create swiper |
Task nolimits4web/SWIPER-79 was created |
@nolimits4web Hi, do you need more information ? |
Task nolimits4web/SWIPER-79 status changed to Done |
@nolimits4web |
not possible |
This was referenced Jun 3, 2024
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
Bug description
Hi,
We use swiper in our project and we occasionally found the error from error monitoring tools (datadog).
The error is come form /swiper/esm/components/scrollbar/scrollbar.js (see attached files).
We try to reproduced the bug but cant. We used to have the same bug in other parts of our code and we solve this with
if (e.cancelable) {
e.preventDefault();
}
In this case, Is it possible to create pull requests for fixed this one.
Our project used
nextjs (v.12.2)
swiper (v.6.8.4)
Expected Behavior
Should not show error in any browser.
Actual Behavior
Error shown up in some error. (We found from monitoring tool)
Swiper version
6.8.4
Platform/Target and Browser Versions
Android/Chrome Mobile
Validations
Would you like to open a PR for this bug?
The text was updated successfully, but these errors were encountered: