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

Back button forgetting?

  • 2 cavab
  • 0 have this problem
  • 4 views
  • Last reply by chrisw63

more options

Several times over the past couple weeks, I click on a Google search result, look at the page, decide it's not exactly what I'm looking for and go to hit Back. Except it's grayed out! I click and hold on the back button and no history pops up!

Even stranger, when I go to History, the search is there! It's like the link not only opened in a new page, but closed the old one!! Is this Firefox doing this to me, or Google's nasty tracking links? Am I the only one?

Several times over the past couple weeks, I click on a Google search result, look at the page, decide it's not exactly what I'm looking for and go to hit Back. Except it's grayed out! I click and hold on the back button and no history pops up! Even stranger, when I go to History, the search is there! It's like the link not only opened in a new page, but closed the old one!! Is this Firefox doing this to me, or Google's nasty tracking links? Am I the only one?

Chosen solution

Extensions like Multi-Account Containers can cause this. Does it still happen in Troubleshoot Mode?

Read this answer in context 👍 1

All Replies (2)

more options

Seçilmiş Həll

Extensions like Multi-Account Containers can cause this. Does it still happen in Troubleshoot Mode?

more options

I do have Multi-Account Containers. After testing... yep... Opening a link that has a container associated with it is the culprit. Totally understandable, since sites in the Back (and Forward) 'history' would be available to the current page if left alone. The only way I can think of to fix that without compromising the 'security' of the container would be to take control of the 'Back' and 'Forward' functions, save those page links in the plugin, marked with whatever containers are involved, and have to close the current tab and open a new one for every back/forward operation - complicated, convoluted, and potentially a memory hog. Now that I know what it is and why it happens, I'll mark this as Solved.

Modified by chrisw63