Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Learn More

Tuta nitka je so archiwowała. Prošu stajće nowe prašenje, jeli pomoc trjebaće.

firefox 119.0.1 won't maintain scroll position upon refreshing

  • 3 wotmołwy
  • 1 ma tutón problem
  • 17 napohladow
  • Poslednja wotmołwa wot 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!

Wšě wotmołwy (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 Prašer
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.