Active threads page keeps reloading from the start

[MsAdoraBelleDearheartVonLipwig]

When I read a thread and then press the back button to go back to the list of active threads, it takes me back to the top of the page rather than where I was on the page like it always used to. Anyone else had this? Bloody annoying, I have to keep whizzing back down all the threads to find where I was.

[LouMumsnet]

Sorry to hear this, OP.

Can you let us know what device/browser you're using to access the site please?

Thanks.

[MsAdoraBelleDearheartVonLipwig]

Thanks Lou. Safari on an iPhone 7.

[LilyMumsnet]

Thank you - how long has this been happening for and if possible, are you able to record a video of it happening for us?

[MsAdoraBelleDearheartVonLipwig]

Oh lord, that sounds a bit technical. It’s been happening for a while. I’ll see if I can forgive out screen recording.

[MsAdoraBelleDearheartVonLipwig]

Well I’ve figured out screen recording but it’s not doing it now! 😄 Have you fixed it?

[MsAdoraBelleDearheartVonLipwig]

Ahh, bugger it, it’s doing it again now. Have screen shot a video. How do I send it to you?

[soniamumsnet]

Hi @MsAdoraBelleDearheartVonLipwig if you're still having problems, please contact us at: [email protected] and we'll take a look.

[MsAdoraBelleDearheartVonLipwig]

Hi, it is doing it again so I’ve emailed you a screen recording.

[Crocky]

Mine is doing this. iPad. But it is also loading the full site on active and the mobile site when in a thread. Driving me a bit bonkers.

[MsAdoraBelleDearheartVonLipwig]

Still doing it. When I’m reading a thread and then go back to the active threads list it goes back to the top of the list. Doing my head in now. I have to whizz all the way back down the list to find where I was. Really putting me off using the site now.

[LilyMumsnet]

Hi OP

So sorry for the delay here - can we ask if this is still happening? We're not sure that it's an issue our end - we would suggest that you update their browser you're using to the latest version, as it's likely an issue with the tracking script.

[Edited to add more information]