Jumping to end of thread
Discussion
I suspect this started happening when the mobile UI was simplified and the "go to new posts" icon was removed, with the href for that object being incorrectly applied to the thread title link.
The problem and solution is super simple. Here's what happens on Desktop:
You can see the HREF for the text is going to the base URL for the thread - i.e. page 1 (depending on what sort order the user has set as their preference). On the "goto newest" link, you can see the &d=xxxxxxx#separator part of the URL that drops to the last page and to the red separator.
Here is the mobile markup:
You can see very clearly that the "last page and separator" link is applied to the whole block which is what you get when you click the title.
If you remove &d=14940.67920#seperator from the href when the user has not visited that thread before (which I assume you know because of the class "topic unread", it will work fine.
I've done the diagnosis for you, are you going to fix it Matt?
The problem and solution is super simple. Here's what happens on Desktop:
You can see the HREF for the text is going to the base URL for the thread - i.e. page 1 (depending on what sort order the user has set as their preference). On the "goto newest" link, you can see the &d=xxxxxxx#separator part of the URL that drops to the last page and to the red separator.
Here is the mobile markup:
You can see very clearly that the "last page and separator" link is applied to the whole block which is what you get when you click the title.
If you remove &d=14940.67920#seperator from the href when the user has not visited that thread before (which I assume you know because of the class "topic unread", it will work fine.
I've done the diagnosis for you, are you going to fix it Matt?
I've just been to one thread I haven't visited in a few years (both in boats, planes) and got taken to the last post (mosquitos) missing a few days of posts, then to the cool pictures thread and off to the top of the last page..... Despite having seen all but the last two posts yesterday.
miniman said:
I suspect this started happening when the mobile UI was simplified and the "go to new posts" icon was removed, with the href for that object being incorrectly applied to the thread title link.
I've done the diagnosis for you, are you going to fix it Matt?
They're not going to fix it! Paying in the thread is as much as they can do.I've done the diagnosis for you, are you going to fix it Matt?
miniman said:
I've done the diagnosis for you, are you going to fix it Matt?
Amazing, really helpful! 
I still can't replicate it on my phone, but that level of detail helps me a lot.
I'm in two minds. I could just remove the seperator tag from the link, but ideally the separator logic would work correctly. However, as usual, the best approach is going to take a lot longer. I can't do much with the code as we turn off the lights over the weekend, but I can at least see the relevant code and what could be done.
Leave it with me and give me a few days to assess and run a solution by the team.
On desktop, it’s easier because you have a separate link for “go to newest posts”.
If you could find space in the UI for a similar link on mobile, that would be your simplest solution. Otherwise you’re going to need to have some logic along the lines of:
If user has previously visited page, insert go to end link
Else insert first page link
Given you can bold / unbold links to shown when they have been visited in My Stuff I imagine you are tracking which users have read which threads but that seems like a processing heavy thing to loop through.
If you could find space in the UI for a similar link on mobile, that would be your simplest solution. Otherwise you’re going to need to have some logic along the lines of:
If user has previously visited page, insert go to end link
Else insert first page link
Given you can bold / unbold links to shown when they have been visited in My Stuff I imagine you are tracking which users have read which threads but that seems like a processing heavy thing to loop through.
miniman said:
Muppet007 said:
Happens all the time when logged in.
Does not when logged out, so I stay logged out most of the time.
Samsung S9 on using Chrome.
That will be because when logged out it can't attempt to figure out when you last visited. Does not when logged out, so I stay logged out most of the time.
Samsung S9 on using Chrome.
I get this too, it's flippin annoying.
Just visited 1275GT's thread on his Vitesse, I've read all 24 pages previously, takes me to page 1.
Other threads I've never read takes me to the end.
I'd really expect it to take me to the last post since I visited a thread, or first page for one I've never opened.
Does it both on my Xperia XA (Android, chrome) and iPhone 7 (chrome).
Just visited 1275GT's thread on his Vitesse, I've read all 24 pages previously, takes me to page 1.
Other threads I've never read takes me to the end.
I'd really expect it to take me to the last post since I visited a thread, or first page for one I've never opened.
Does it both on my Xperia XA (Android, chrome) and iPhone 7 (chrome).
Pinkie15 said:
I get this too, it's flippin annoying.
Just visited 1275GT's thread on his Vitesse, I've read all 24 pages previously, takes me to page 1.
Other threads I've never read takes me to the end.
I'd really expect it to take me to the last post since I visited a thread, or first page for one I've never opened.
Does it both on my Xperia XA (Android, chrome) and iPhone 7 (chrome).
Precisely, you're describing exactly what happens now and exactly how logic suggests it should work. Just visited 1275GT's thread on his Vitesse, I've read all 24 pages previously, takes me to page 1.
Other threads I've never read takes me to the end.
I'd really expect it to take me to the last post since I visited a thread, or first page for one I've never opened.
Does it both on my Xperia XA (Android, chrome) and iPhone 7 (chrome).
I don't think PH have any developers to be honest.
miniman said:
I don't think PH have any developers to be honest.
Hello. There's 6 of us and we're all flat out.We've been looking into this issue and we've found a few edge cases to consider. It's unfortunately not as simple as removing the #separator value in the URL as there's some lovely code in there doing device detection and going off to the database to take you to (what it thinks is) the right page, depending on your forum settings, which needs to be properly evaluated and tested.
If this forum wasn't written in Classic ASP we could move a lot quicker for you.
Gassing Station | Website Feedback | Top of Page | What's New | My Stuff