This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Rohkem teavet

Teema arhiveeriti. Please ask a new question if you need help.

firefox 119.0.1 won't maintain scroll position upon refreshing

  • 3 vastust
  • 1 on selline probleem
  • 8 views
  • Viimati vastas flemingp

il626
il626
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!

All Replies (3)

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

il626
il626 Küsimuse esitaja
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

flemingp
flemingp
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.