Avatar for Username

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Toś ta nitka jo se archiwěrowała. Pšosym stajśo nowe pšašanje, joli trjebaśo pomoc.

Back button forgetting?

  • 2 wótegronje
  • 0 ma toś ten problem
  • 4 naglědy
  • Slědne wótegrono wót chrisw63

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

Wubrane rozwězanje

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

Toś to wótegrono w konteksće cytaś 👍 1

Wšykne wótegrona (2)

zeroknight
zeroknight
more options

Wubrane rozwězanje

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

chrisw63
chrisw63 Pšašaŕ
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.

Wót chrisw63 změnjony