Not working with iOS 11.3 Mobile Safari
See original GitHub issueIt looks like the workaround
window.addEventListener( 'touchmove', function() {});
doesn’t work anymore with iOS 11.3 Mobile Safari. Is there a new workaround? 😅 It looks like that the same issue applies to Chrome on iOS as well.
Issue Analytics
- State:
- Created 5 years ago
- Comments:14
Top Results From Across the Web
iOS 11 Safari Not Working on iPhone 6/6S/7/7 Plus? Fixed Here!
7 Tips to fix Safari not working in iOS 11 on iPhone 6/6S/7/7 Plus · 1. Close and launch Safari again · 2....
Read more >Top 12 Ways to Fix Safari Not Working on iPhone and iPad
1. Restart iPhone or iPad · 2. Turn off Safari Suggestions · 3. Edit Your Screen Time Settings · 4. Check Cellular Settings...
Read more >Safari Not Working On iPhone? Here's The Fix.
What's Really Causing The Problem? · Close And Reopen Safari · Clear Safari History And Website Data · Restart Your iPhone · Update...
Read more >Safari Not Working On iPhone? Try These Tips To Fix It
When Safari starts misbehaving on an iPhone, with random crashes or websites that never load properly, there are several possible solutions.
Read more >Top 11 Fixes for Safari Not Working on iPhone and iPad
1. Closing Your Safari Tabs. The first thing to try to fix Safari not working on your iPhone or iPad is to close...
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
Turns out the same workaround still applies but because Safari on iOS 11.3 enables passive event listener support it defaults to
passive: true
for event listeners on document level.The fix is simple:
But this puts the burden of feature detection of passive event listeners on the polyfill user. Maybe I should put this into another augmentation module so people who need to support Safari just import and apply a single
makeItWorkOnSafari()
function…If you need to support older browsers (e.g. previous Safari) the third parameter on
document.addEventListener()
would be interpreted either ascapture
parameter or something else unintended happens.To correctly apply the different workarounds you now have to check for passive event listener support and act accordingly