(5.x) preventDefaultTouchmoveEvent (Mobile Safari?)
See original GitHub issueHi and thanks for all your work.
I can’t seem to prevent vertical scrolling during a left/right swipe using preventDefaultTouchmoveEvent
with 5.x where 4.x works fine (iOS 12.1.4, React 16.8.3). I’m using it with onSwipedLeft
and onSwipedRight
and everything else default. Seeing same behavior in the example actually; any ideas or anyone else experiencing this?
Issue Analytics
- State:
- Created 5 years ago
- Comments:12
Top Results From Across the Web
Handling Events - Apple Developer
You can disable the default browser behavior by sending the preventDefault message to the event object.
Read more >Preventing touchmove events in a <video> element in Mobile ...
I am writing a home-screen web app with a video element in Mobile Safari. For usability reasons, I would prefer that swiping on...
Read more >Touch events - Web APIs - MDN Web Docs - Mozilla
This calls event.preventDefault() to keep the browser from continuing to process the touch event (this also prevents a mouse event from also ...
Read more >Making touch scrolling fast by default - Chrome Developers
We know that scrolling responsiveness is critical to the user's engagement with a website on mobile, yet touch event listeners often cause ...
Read more >184250 – Unable to call event.preventDefault in dynamically ...
I can confirm this for: - Safari 11.3 on Mac OS X 10.13.3 - Safari 11.3 on iOS 11.3 Any drag and drop...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
react-swipeable@5.1.0-alpha.2
Still on target to release
5.1.0
this week.What we’ve discovered so far:
v5
’s change to how it listens totouchmove
eventstouchmove
listener directly to the elementtouchmove
listener BEFORE the touchstart event startedtouchmove
listener to document nowtouchmove
listener AFTER the touchstart event startstouchmove
todocument
appears to work fine for chrome, though there are some events that throw warnings #128Bug report(s) from around the web: