diff options
| author | Peter Stone <thepeterstone@gmail.com> | 2026-09-02 23:14:33 +0000 |
|---|---|---|
| committer | Peter Stone <thepeterstone@gmail.com> | 2026-09-02 23:14:33 +0000 |
| commit | 0642dab358ac7c84d56314277d4664043598dcc5 (patch) | |
| tree | 1c170f3d7be658af82ca493a36d8431de03f9294 /Makefile | |
| parent | a17a15966be5db6de423cdcb7c427195102b99d8 (diff) | |
Restore WebView state across Activity recreation in the dashboard widget
The web dashboard is a single HTMX page -- tab switches are client-side
swaps + history.pushState (?tab=shopping), never a real navigation. The
WebView never saved/restored that state, so any Activity recreation
(Android reclaiming a backgrounded Activity, a rotation, anything that
reruns the AndroidView factory with a fresh WebView) fell back to
loadUrl() on the bare server URL in the update block, landing on
whatever tab is default. Reported as "shopping randomly jumps back to
timeline" -- the prior swipe-detection fix (a17a159) addressed a real
but separate false-positive source and didn't touch this path, which
isn't tied to touch input at all.
WebView.saveState/restoreState is the standard mechanism for exactly
this; wired into onSaveInstanceState and the AndroidView factory.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018AwnALZL6bD4VBtATDVv3B
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions