Close the photo, keep the page
Closing a photo used to remount the page behind it, collapsing expanded replies and jogging your scroll. Now the page stays live through Close, Back, Forward, and slide changes.
You're deep in a Log thread with replies open, you click a photo, then you hit Close. The photo goes away and the thread is still there. The same replies are expanded, the scroll is the same, and the same picture sits where you left it. No flash, no jump, no reload.
Credit goes to xHeaven, who taught the viewer to keep the page behind it alive. Each photo visit gets a session ID and an entry ID, both random, so two trips to the same photo URL stay distinct. On Back or Forward the app cancels pending requests, reads the saved page from Inertia's history even when that history is encrypted, checks the app version, then restores the photo with scroll and state preserved. While a photo is open, background polling still asks the page underneath for new commits.
There is one catch. The session dies on reload. Open a photo, hit Reload, and Close no longer walks you back to the Log. It drops you on the commit page instead, and Back won't find the old thread. A direct photo link always closes to its commit, since it never had a page behind it.