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 define a swipe (like swipe right) handler and a tap handler for one element, a swipe will result in both handlers being triggered.
So if you have some sort of gallery--you would like to swipe through and then tap on one of the options to see more. At the moment, every swipe will act as a tap.
The text was updated successfully, but these errors were encountered:
if you define a swipe (like swipe right) handler and a tap handler for one
element, a swipe will result in both handlers being triggered.
So if you have some sort of gallery--you would like to swipe through and
then tap on one of the options to see more. At the moment, every swipe will
act as a tap.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/29.
That's not really an option for this project, but I'll keep it it mind for the future.
I found a workaround--if you put the tap handler on an ancestor of the element with the swipe handler, it will act appropriately on mobile browsers (not on desktop browsers though).
if you define a swipe (like swipe right) handler and a tap handler for one element, a swipe will result in both handlers being triggered.
So if you have some sort of gallery--you would like to swipe through and then tap on one of the options to see more. At the moment, every swipe will act as a tap.
The text was updated successfully, but these errors were encountered: