You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! The carousel drag is becoming unresponsive when you use the next() method. This is only happening if the number of slides to be shown is larger than number the slides available. Here an example with 4 slides and 5 perPage slides showing this behaviour.
More info that may help
This seems to affect only next().
The carousel will work as expected when passing a number with the goTo() method.
currentSlide is returning -1 when next() is used.
The text was updated successfully, but these errors were encountered:
It is a good sport that next() method changes value from 0 to -1. Is is a bug but not major one as it doesn't affect carousel functionality — it will be fixed though. The issue to resolve here is not inside next() method. The problem is with goTo() method as it shouldn't slide items in a manner that leaves an empty gaps on the end of a selector — it is bad UX.
I still consider this as an edge case scenario because a main purpose of using carousel is to slide items when there is not enough of room for it. Nobody is using carousel to waste space on the screen.
Probably the best thing here wold be preventing user from invoking any method like next(), prev() or goTo() when there is no need for them.
It is easy fix and edge case. It will be fixed in next minor release. Thanks 🍻
What is happening
Hi! The carousel drag is becoming unresponsive when you use the
next()
method. This is only happening if the number of slides to be shown is larger than number the slides available. Here an example with 4 slides and 5 perPage slides showing this behaviour.More info that may help
next()
.goTo()
method.currentSlide
is returning-1
whennext()
is used.The text was updated successfully, but these errors were encountered: