Join us and the lead editor of IRL, Mozilla's multi-award-winning podcast, for a behind-the-scenes look at the pod and to contribute your ideas for the next season, themed: "AI and ME." Mark your calendar and join our Community Call on Wednesday, Aug 7, 17:00–17:45 UTC. See you there!

Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër

firefox 119.0.1 won't maintain scroll position upon refreshing

  • 3 përgjigje
  • 1 e ka hasur këtë problem
  • 17 parje
  • Përgjigjja më e re nga flemingp

more options

Hello there.

I've notice FF in the past month has stooped maintaining scroll position upon refreshing. It was working perfectly until recently. maintain scroll position upon refreshing is a key feature to my work. Please help!

Hello there. I've notice FF in the past month has stooped maintaining scroll position upon refreshing. It was working perfectly until recently. maintain scroll position upon refreshing is a key feature to my work. Please help!

Krejt Përgjigjet (3)

more options

Doing a hard refresh with Ctrl+F5 will reset the scroll position.

Does it happen for all sites or one in particular?

Does it still happen in Troubleshoot Mode?

more options

zeroknight said

Doing a hard refresh with Ctrl+F5 will reset the scroll position. Does it happen for all sites or one in particular? Does it still happen in Troubleshoot Mode?

Just normal refresh. All sites. Other browsers works just fine with same site, scroll position is maintained after multiple refreshes

more options

I'm having the same issue, only not just page refresh but also when I click on a link and then hit the 'go back' button the page will return with the scroll position at the top instead of in the position it was in prior to hitting the link. I've read several bug reports for this going back 20 years. Apparently this has happened many times and seems to have been fixed each time.