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
{{ message }}
This repository has been archived by the owner on May 15, 2023. It is now read-only.
Swipeable elements within the iron-swipeable-container prevent the page from vertically scrolling, even when they have the disable-swipe attribute.
Maybe this is related to issue #5 as it seems to me that vertical scrolling should be given priority over swiping which should occur only after a certain distance.
The text was updated successfully, but these errors were encountered:
I was looking into the source and noticed it seemed to be caused by the track event.
Wish there was a way to only have horizontal/vertical tracking events.
(I also prevented swiping to the right (swipe left only) and made the swipe effect only effective after some time to prevent the swipe effect while just scrolling : you might want to remove that before using this modified element)
I also didn't update the tests and didn't check if the demo passes, so not ready at all for a push request right now ;)
I'm also experiencing this myself. I'm writing a photo gallery and I want the ability to swipe right/left to go to the next or previous image. It works great, but it seems the track event prevents any vertical scrolling. Maybe, if the component detects a positive or negative change in the y coordinate, and the change in x is small, the page could scroll. This is only an issue on mobile, but that's primarily where the user would want to swipe anyway. I love the element otherwise!
Swipeable elements within the
iron-swipeable-container
prevent the page from vertically scrolling, even when they have thedisable-swipe
attribute.Maybe this is related to issue #5 as it seems to me that vertical scrolling should be given priority over swiping which should occur only after a certain distance.
The text was updated successfully, but these errors were encountered: