summaryrefslogtreecommitdiff
path: root/app/src/main/java/org/terst/feedreader/readability
diff options
context:
space:
mode:
authorPeter Stone <thepeterstone@gmail.com>2026-07-25 04:03:11 +0000
committerPeter Stone <thepeterstone@gmail.com>2026-07-25 04:03:11 +0000
commit19bfb97fb30b7bfc861d1d17c3b406e6157f6d02 (patch)
treefdeb121f34ac3ed9c0e147eeaba2ba46f2a10a69 /app/src/main/java/org/terst/feedreader/readability
parente69da36b9ba2d79c383802d387084cf555169566 (diff)
Fix BrowserScreen back button: step through page history before closing
Reasoned through the code rather than reproducing live (per explicit instruction). An earlier change made back always close the whole browser screen in one press, regardless of how many pages deep the session was -- on the theory that stepping back one page at a time through a long search/login session was tedious. That trade was wrong: it meant a single accidental back press (system gesture or the in-app arrow) could silently destroy an entire multi-page browsing session with no way to recover it, and it doesn't match how every other browser or in-app browser view on the platform behaves. Now: go back through the WebView's own page history first (canGoBack()/goBack()), and only close the screen once there's nowhere left to go back to. Both the system back gesture and the in-app top-bar arrow route through the same handleBack(), so they behave identically. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EZ7ikw2ukGJFTHE3bJS7zL
Diffstat (limited to 'app/src/main/java/org/terst/feedreader/readability')
0 files changed, 0 insertions, 0 deletions