I browse a mobile website on an Android phone using the Brave browser. When I open the home page, select an article, and swipe from the left edge toward the center to go back, I often end up at the top of the home page or on a blank page, losing my previous position. However, swiping from the right edge toward the center usually returns me to the exact spot I expected. I haven't noticed this behavior on other sites. Is Android or Brave treating the two edge gestures differently, or is the site's JavaScript competing with the browser's navigation gesture?
3 Answers
This doesn’t seem to be limited to Brave—I’ve seen the same thing in Chrome on Android. It may be a regression in the mobile site rather than a browser-only bug. Opening articles in new tabs is one workaround, although using the opposite edge for the back gesture is much less disruptive.
Brave may have a more aggressive gesture zone, but the underlying issue is likely the page’s history and touch handling. If a page uses JavaScript to intercept swipes or update its own navigation state, the browser’s left-edge back gesture can trigger both behaviors at once. The right-edge gesture avoids that particular collision.
The site and the browser are probably competing for the same gesture. A left-edge swipe is commonly reserved by Android or the browser for its native back navigation, while the site may also interpret it as an in-page navigation gesture. That conflict can cause the page to reload, jump to a different history entry, or lose its scroll position. The right-edge swipe appears to reach the site’s own navigation logic more reliably, so it behaves normally.
Related Questions
How to Build a Custom GPT Journalist That Posts Directly to WordPress
Cloudflare Origin SSL Certificate Setup Guide
How To Effectively Monetize A Site With Ads