83
votes

For some web pages we use the swipe left and right functionality of iPhone to pull up the menus. Now with iOS7, they have introduced the ability to go back and forward to previous and next pages of browser history on swipe left and right motions.

But is there a way to disable it for specific pages so as to not have conflicting behavior on the swipe actions?

3
It should be distinguished by the swipe starting offscreen. Do you have an example webpage where a conflict occurs?Rupert Rawnsley
@RupertRawnsley Add a touchstart/touchmove event to your web page with a console.log('FIRED!'); in it. Move your finger onto the web page from the edge and you will notice the event never fires. Am I right in assuming that this will be the new expected behavior?Marcus
+ 1 for this. Troublesome when you swipe to open a menu.TYRONEMICHAEL
+1 The user has no idea what a offscreen swipe versus an onscreen swipe is. Blergh!Joseph Juhnke
As a user with poor eyesight I need to zoom a lot and pan, that swipe back gesture drives me insane. If anyone knows how to disable it I want to know.Brett Ryan

3 Answers

15
votes

No, this is done at the OS level, and webpage doesn't get any callback

See this summary of safari changes in iOS7 that might cause problems to your website (including this swipe gesture)

13
votes

You can't disable it directly, but the native swipe back only happens if there is something in the browser history.

It won't work in every case, but if you have a single page web app opened in a new tab, you can prevent it from adding to the history by using

window.history.replaceState(null, null, "#" + url)

instead of pushState or

document.location.hash = url
7
votes

I had to use 2 approaches:

1) CSS only fix for Chrome/Firefox

html, body {
    overscroll-behavior-x: none;
}

2) JavaScript fix for Safari

if (window.safari) {
    history.pushState(null, null, location.href);
    window.onpopstate = function(event) {
        history.go(1);
    };
}

Over time, Safari will implement overscroll-behavior-x and we'll be able to remove the JS hack