-
Notifications
You must be signed in to change notification settings - Fork 233
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
Bugfix: Carousel Swiper Styling & Direction #1023
Conversation
Run & review this pull request in StackBlitz Codeflow. |
The latest updates on your projects. Learn more about Vercel for Git βοΈ
|
β¦ goes back, right->left goes forward)
f1f401b
to
3a589b6
Compare
On an iPad, swiping works but all buttons don't work. Can you have a look at it? |
So I don't have a physical iPad to test with @shinokada, but I was able to reproduce in Chrome & Safari browser emulator. It also appears that it's not just the iPad, but the buttons are not working on any mobile device (including my Pixel Android phone). Looks like the problem is caused on mobile devices because I was able to fix this by saving the original browser event when the user first touches and then manually issuing "tap" gesture click handling if under the drag threshold (thus considered a "tap" instead of a "drag"). Tested working in iPad Browser Emulator in Chrome/Safari and on actual Pixel phone |
35aadf6
to
df5b79e
Compare
Thanks for the fix. |
π Description
This PR fixes the custom Carousel styling which was lost when adding swiper component by re-adding custom
imgCls
andslideCls
.This PR also inverts the order of the carousel swiper direction to match expected behavior from other swiping libraries such as SwiperJS (swipe from left->right to go back, right->left to go forward).
See: #965
Status
β Checks