Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Learn More

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

Burned By An Update To 86.0!

  • Keine Antworten
  • 1 hat dieses Problem
  • 13 Aufrufe
Steve_Sr.
Steve_Sr.
more options

Hello,

Just updated after a long time from 66.0.5 -> 72.0.2 -> 86.0. This is what FF wanted to do for some unexplained reason so I just let it.

Now when I open a new tab in an open window I get a white screen and nothing works. Entering a URL in the bar or pressing any of the buttons like home does nothing whatsoever. Just a blank white screen.

This is why I LOATHE updating anything! The odds of breaking something that was working perfectly is VERY high. Proved the point once again. I used to let FF update itself and then got burned by the Quantum update that trashed ALL of my open session windows. Turned auto-update OFF after that so that could manually grab and save a copy of the profile BEFORE any update happens.

So how do I fix this or is it a legitimate BUG that should be reported (and how to do same)?

Thanks, Steve

Hello, Just updated after a long time from 66.0.5 -> 72.0.2 -> 86.0. This is what FF wanted to do for some unexplained reason so I just let it. Now when I open a new tab in an open window I get a white screen and nothing works. Entering a URL in the bar or pressing any of the buttons like home does nothing whatsoever. Just a blank white screen. This is why I LOATHE updating anything! The odds of breaking something that was working perfectly is VERY high. Proved the point once again. I used to let FF update itself and then got burned by the Quantum update that trashed ALL of my open session windows. Turned auto-update OFF after that so that could manually grab and save a copy of the profile BEFORE any update happens. So how do I fix this or is it a legitimate BUG that should be reported (and how to do same)? Thanks, Steve