Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

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.

Learn More

This thread was archived. Please ask a new question if you need help.

When returning from page with the back button, it puts you to the top of the previous page. How can I return to part of page where I clicked from vs. the top?

  • 1 reply
  • 1 has this problem
  • 11 views
  • Last reply by Paul

acollosi
acollosi
more options

I have a problem from when I enter a search result, then scroll down to the middle of a page, click on a link to take me to a new page. The problem is when I click back to return to the search results it takes me to the top of the page instead of the middle of the page where I was exploring the results.

This is very frustrating with constantly having to scroll back down to the results as I explore (click & back) the results.

I have a problem from when I enter a search result, then scroll down to the middle of a page, click on a link to take me to a new page. The problem is when I click back to return to the search results it takes me to the top of the page instead of the middle of the page where I was exploring the results. This is very frustrating with constantly having to scroll back down to the results as I explore (click & back) the results.

All Replies (1)

Paul
Paul
  • Top 25 Contributor
  • Moderator
more options

Hi

I am aware of this issue and I believe it is currently being looked into by our developers. Hopefully you should see this fixed in a future update.