goto first new post broken with Chrome on Windows?

[sanddrag]

Given that the problem persists across different browsers and devices, I'm thinking it's not a browser-side problem. So, how do we send this up the ladder to someone who can look into it deeper? There's clearly several of us who are having the problem.

[EricH]

Originally Posted by sanddrag

Given that the problem persists across different browsers and devices, I'm thinking it's not a browser-side problem. So, how do we send this up the ladder to someone who can look into it deeper? There's clearly several of us who are having the problem.

Sent up the ladder. Sometimes a PM can bring attention to the problem in ways that a half-buried thread can't.

[Brandon Martus]

Thanks for the PM EricH.

I'll take a look at this sometime this weekend.

[Brandon Martus]

I'm having trouble reproducing this issue. If someone has this happening, can you reply with a screenshot of when the page loads, as well as the URL you are on? Thanks.

[EricH]

Originally Posted by Brandon Martus

I'm having trouble reproducing this issue. If someone has this happening, can you reply with a screenshot of when the page loads, as well as the URL you are on? Thanks.

See attached, going from Portal just now. (Blocked out a couple of tabs)
And another from the "first unread" on the thread, same thing.

BTW, this is Firefox 50.1.0, operating on Windows 10 Home with everything up to date.

[cgmv123]

Chrome 55 on Windows 10

[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?