(no subject)

[alexseanchai]

this is a Firefox problem, right?

because it is now happening on multiple devices. I had my reading page scrolled down a bunch, but not far enough to get to my post about accidentally a new chapter of swallow my doubt. I clicked through to a post, I backbuttoned, and I was looking at a different post entirely, and when I got back to the top of my reading page, the most recent post it showed was I accidentally a new chapter of swallow my doubt. still Firefox 68.0.2 but this is the version for Windows 10.

Comments

[sporky_rat]

Check with Support.
(Someone can do more digging.)

[alexseanchai]

Shall

[mdlbear]

It does not appear to be happening in Firefox 68.0.2 on Ubuntu. I also tried it with your DW to see whether it's an issue with your format; it doesn't appear to be.

I can see something like this happening if you followed a link to that post; i.e. that post's position on your reading page.

ETA: I made this comment inline and still got expected behavior. But I see that your reading page, like mine, has a page summary. All the links in that summary point to specific posts, e.g. read#entry-00000. But in that case, going back would go to that post, but it would no longer be the most recent and you could scroll up to see newer posts.

[alexseanchai]

I don't use the page summary, though. I'm not sure if it's taking me back to (say) the eighteenth entry on the version of my reading page that's one refresh ago, when the link I clicked was the permalink for the eighteenth entry on the most recently refreshed version, or if it's taking me to that place on the vertical scroll. (The latter definitely happens when I expand a cut tag with a lot behind it, forget to collapse it, click through to something, and back button. The cut tag collapses itself somewhere in there, so I end up farther down than I thought I was.)