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
In previous version of slider - https://github.com/kenwheeler/slick/ We can slide to next or previous simply by clicking the inactive but current slides on either sides of the active and current slide card.
But in the new accessible 360 version, that feature seems not working or removed without any mention anywhere.
See the example of previous - working one here - https://kenwheeler.github.io/slick/ - scroll to "Slider Syncing" example and click on slide card no. 5 and 2 - The slider will slide left or right.
Now check the sample of new accessible 360 slider - https://accessible360.github.io/accessible-slick/ - Scroll to "Slider Syncing" example section and try to click on same slide card no 5 and 2. The slider wont slide anywhere. This seems like an omitted feature without any mention anywhere. Can anyone please comment here or help how to get it back.
Please write back to [email protected]
The text was updated successfully, but these errors were encountered:
In previous version of slider - https://github.com/kenwheeler/slick/ We can slide to next or previous simply by clicking the inactive but current slides on either sides of the active and current slide card.
But in the new accessible 360 version, that feature seems not working or removed without any mention anywhere.
See the example of previous - working one here - https://kenwheeler.github.io/slick/ - scroll to "Slider Syncing" example and click on slide card no. 5 and 2 - The slider will slide left or right.
Now check the sample of new accessible 360 slider - https://accessible360.github.io/accessible-slick/ - Scroll to "Slider Syncing" example section and try to click on same slide card no 5 and 2. The slider wont slide anywhere. This seems like an omitted feature without any mention anywhere. Can anyone please comment here or help how to get it back.
Please write back to [email protected]
The text was updated successfully, but these errors were encountered: