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.

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.

Learn More

Using the back button returns me to the top of the page I left rather than the location from which I followed a link.

  • 5 replies
  • 4 have this problem
  • 2 views
  • Last reply by cor-el

more options

If I load a page and scroll down, then follow a link, then use the back button I end up at the top of the page, not at the location from which I followed the link. Started happening after updating to version 19.0, on Windows 7 Professional 64-bit machine.

If I load a page and scroll down, then follow a link, then use the back button I end up at the top of the page, not at the location from which I followed the link. Started happening after updating to version 19.0, on Windows 7 Professional 64-bit machine.

All Replies (5)

more options

hello, can you try to replicate this behaviour when you launch firefox in safe mode once?

Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems

more options

You can also check on the about:cache page if the disk cache is enabled and working.

In case you are using "Clear history when Firefox closes":

  • do not clear the "Cache" because Firefox will disable the disk cache in such a case
more options

I did try that (safe mode), with no difference in behavior. However, I did notice that the behavior seems to be site-specific. Where I first noticed it was on Engadget.com (hasn't done that before on that site). Also seems to happen on msn.com. However, it does not behave that way on other sites, such as finance.yahoo.com.

Modified by tswright

more options

I checked on the cache settings - disk cache is on and appears to be working; no offline caching. Clearing the cache on exit is turned off.

more options

That can be caused by the no-cache in the response headers:

  • Cache-Control:no-cache, must-revalidate, post-check=0, pre-check=0