goto first new post broken with Chrome on Windows?

[engunneer]

i've been experimenting with what i need to do to fix this (happens to me on firefox too). Deleting the sessionhash cookie helps. I think it is somehow used to calculate what anchor to link to when navigating the goto=newpost links on the portal page. Incidentally, I only ever browse from the portal page, so maybe this doesn't happen in the forums proper. Might be a bug with whatever engine generates the postid?

[MrForbes]

it's not working right for me...has not been for months....but it seems to be that when there are more than one page, it gets stuck on the first page? It does go to the first unread post on short threads, usually.

Sure is an annoying problem, that didn't used to be there.

I'm using firefox on win 7, and between when the problem started and now, I am running a new installation of windows and of firefox.

[bdaroz]

Originally Posted by MrForbes

it's not working right for me...has not been for months....but it seems to be that when there are more than one page, it gets stuck on the first page? It does go to the first unread post on short threads, usually.

Not much to add except "me too". I find myself all too often clicking the link to goto the last post and scrolling up especially on very large threads.

[MrForbes]

And this morning, it's working.

I wonder if it will be working this afternoon?

[ATannahill]

Originally Posted by MrForbes

And this morning, it's working.

I wonder if it will be working this afternoon?

Not for me.

[Jon Stratis]

It's rather inconsistent. For example, I visited a thread right before this that I had read before, and it went straight to the correct post. Visited this thread, and I got sent to the same post I read 2 hours ago. The URL was:
https://www.chiefdelphi.com/forums/s...83#post1633383

This URL appears to be pointing to the post I was taken to (post #24) instead of the post I should have been taken to, post #25. I know, it's a small difference... but on longer threads that ends up being pages of posts different.

I'm not sure how the site stores the most recent post read, but I'm guessing that would be a good starting point, as the link itself doesn't seem to be generated to point to the correct post.

[engunneer]

I think the forum calculates using the time you last visited the thread (stored in a cookie) compared to the post times. if the cookie is not updating, it will keep calculating an older post number. It's certainly cookie based and not database backed because i have threads that link to one post on this computer and a different post in the same thread on my home computer.

the calculation for which post to jump to is calculated when you click the new post link, not when it loads the list of links (which makes sense from a processing time point of view, as on demand is less load then always calculating all.)