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
If you click on the second dot, the bullet does not get the glide__bullet--active. However if you scroll through from the start it will get an active class.
It seems to be a problem if you are "jumping" ahead to a custom slide index. Would imagine it being a problem for the API too.
If this is intended, then it's a bit odd that the dots will allow you to navigate in any direction yet doesn't work out where about's you have navigated to in the slider relative to the number of dots available. That really should be mentioned in the docs if such a scenario is not supported.
In our case, we don't want each dot to represent a slide, but instead each dot should represent navigating to the next set of visible slides per view - so for example if we're showing 6 per view, we would like to jump in increments of 0, 6, 12, etc.
Chiming in with a workaround in case anyone else got here from googling:
Since addClass() uses the index of the active slide, you can get around this limitation by defining the bullets for every slide but hiding (e.g. with CSS) every unwanted nth bullet.
Reproducable on: https://codepen.io/garygreen/pen/Owvmgr
If you click on the second dot, the bullet does not get the
glide__bullet--active
. However if you scroll through from the start it will get an active class.It seems to be a problem if you are "jumping" ahead to a custom slide index. Would imagine it being a problem for the API too.
You also get an error in console:
Relating to these line:
glide/dist/glide.esm.js
Lines 3142 to 3153 in 32c7d4e
The text was updated successfully, but these errors were encountered: