-
The forum knows how many posts were in the thread when you last looked at the thread or which was the last page of the thread you looked at if there are further unread pages, so when you next visit the thread it tries to position you at the next unread post.
The problem is usually images. The HTML page tries to tell the browser where to scroll down (probably using html element references) but pictures loading (or not loading as expected) screw up the positioning and the browser tries to minimise jumping around so it ends up with you looking at the wrong thing usually.
-
I have no real idea how this works, does the site somehow know when you've 'seen' a post, or does it know how many posts there were when you last looked at the page?
The site keeps track of the timestamp of the last comment on a page of comments. It knows you have "seen" up to there.
But... if a new comment is 20 comments down a page, and comments higher have inlined images from slow 3rd party servers... then when you arrive at the new comment, it may be pushed down the page by the loading of images higher on the page.
You are reading a single comment by @yoshy and its replies.
Click here to read the full conversation.
Greenbank
Velocio
@yoshy
Why is it that sometimes when I revisit a thread, I'll be taken back to a post I've already read before?
I have no real idea how this works, does the site somehow know when you've 'seen' a post, or does it know how many posts there were when you last looked at the page?