Swiper: Mousewheel Failing

Created on 3 Dec 2019  路  8Comments  路  Source: nolimits4web/swiper

This is a (multiple allowed):

  • [x] bug
  • [ ] enhancement
  • [ ] feature-discussion (RFC)

What you did

The mousewheel scrolling fails intermittently. need to scroll a lot of time to move one slide.

Expected Behavior

Free scroll with mousewheel

Actual Behavior

Mousewheel slider control does not function

this problem was discussed here: https://github.com/nolimits4web/swiper/issues/2624 but didn't see any solution for this problem.

stale

Most helpful comment

I found this phenomenon is occasional, but the probability of it is quite high, especially when two-finger swipe on the macbook is obvious.This problem exists in 5.2.1, 5.2.0 and 4.5.3 that I tried. There is no good solution so far, and it is not clear where the problem lies. The official demo has also this problem.

All 8 comments

Seeing #2624 i thought, could this have something to do with the grab simulation? In the API the grabCursor only 'fires' after the mouse is clicked and then dragged. If this same behaviour is in the scrollEvent i can see why scrolling has to happen multiple times.

Just a thought, will dive into this :)

I found this phenomenon is occasional, but the probability of it is quite high, especially when two-finger swipe on the macbook is obvious.This problem exists in 5.2.1, 5.2.0 and 4.5.3 that I tried. There is no good solution so far, and it is not clear where the problem lies. The official demo has also this problem.

This problem affects only mousewheel, touchpad is still working.
I've faced this problem on every browser, and there is also another bug: when you pass an object to mousewheel property, it doesn't enable it, only mousewheel: true is working

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.

No fix yet?

I've checked in version 6.0.4 - it's functions normally

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.

This issue has been automatically closed due to inactivity. If this issue is still actual, please, create the new one.

Was this page helpful?
0 / 5 - 0 ratings