Users reported a bug where the read post position in topics no longer returns to the last viewed post, instead jumping to a different position, sometimes after clicking notifications or opening topics. The issue began after enabling the sidebar and coincided with a recent code commit. Don provided video evidence showing the behavior, while robotnjik and stuwest confirmed similar issues. cvx clarified that the system is supposed to take users to the first unread post, not the last viewed position, and acknowledged that the scroll-to-last-seen-line feature is buggy. The issue may be related to delayed loading of posts or deleted content. sam confirmed the issue is being tracked by engineers. Don later confirmed the problem was resolved after reverting a commit, suggesting the issue was likely caused by that change.
I noticed when I go to a topic where I earlier read a few post than it will not continue from that post where I stoped reading.
Now it seems to the read position is the onscreen last post instead of the onscreen first post.
Demo: On the video I scroll to the 14th post and go back to topic list. Than I open it again and it goes to the 18th post instead of 15th.
Yeah something changed because it should also scroll to the last seen line. I think I move it to Contribute > Bug.
Edit: It seems to it jumps to the last seen line when the post highlight animation ends.
This is because the last seen line is only shows up after the highlight animation (or post loads).
Sorry for bumping but is there any update with this? I noticed also sometimes when I click a notification on menu than it jumps a few posts above than where the notification links.
Nope, I think not the sidebar. Maybe partly cause this commit DEV: Asyncify loadTopicView (#18585) · discourse/discourse@2c5e8f1 · GitHub ? Because it seems to topic elements posts, last seen line etc… load a little delay and I think this is why it jumps to a random posts sometimes. But I am not sure
I believe that’s how it’s supposed to work? Clicking on a topic in a list takes you to the first unread post*, not your previous position. You can go back to the spot you left using browser’s back/forward navigation.
(* – there are settings, that slightly change that - i.e. navigate_to_first_post_after_read category setting that, if enabled, navigates you to the first post if you don’t have any unread posts left in a topic)
Yup, scroll to the “last visit” marker is a bit buggy. It won’t work if there are any small-posts (like “X months later”) or deleted posts right after it. I’m working on a fix.
