aboutsummaryrefslogtreecommitdiffstats
path: root/tools/thread-back-scroll-test.js
diff options
context:
space:
mode:
authorAdam Soltys <[email protected]>2026-10-11 22:39:04 -0700
committerAdam Soltys <[email protected]>2026-10-11 22:39:04 -0700
commit880abf73720acc13e07242568d56c14bca247c5e (patch)
tree54ccc60ff0bbfccf1e23a78246f8694b2dab04a6 /tools/thread-back-scroll-test.js
parent8b65caee4348073f44c36d379bc654c27f5e9ee5 (diff)
downloadcoinosv3-880abf73720acc13e07242568d56c14bca247c5e.tar.gz
coinosv3-880abf73720acc13e07242568d56c14bca247c5e.zip
Feed: closing a full-screen picture leaves the feed where it was. The scroll memory that puts a reader back on the row they left when Back closes a thread or profile fired on every history pop, and a remembered place goes stale whenever its page is left another way (the Feed button from a thread), so a photo's × jumped the feed to wherever an earlier thread had been opened from, or to its top (Adam's recording, 2026-10-11 22:31, at the 10 s mark; reproduced on his tab: 2500 → 22361). Now the place is restored only when a pop actually leaves a thread or profile — the page being left is read in a capture-phase popstate listener, before the app's own handler re-renders — and the entries above the one it matches are dropped as stale. tools/lightbox-scroll-test.js (stale place from a thread left by the Feed button, a picture opened and closed, Back out of a thread still landing on its row). avatar-profile-test fails on HEAD before this too.
Co-Authored-By: Claude Fable 5.1 <[email protected]>
Diffstat (limited to 'tools/thread-back-scroll-test.js')
0 files changed, 0 insertions, 0 deletions