Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Disabling Forced What's New Page Loading

  • 1 antwurd
  • 0 hawwe dit probleem
  • 2 werjeftes
  • Lêste antwurd fan zeroknight

Waffaru
Waffaru
more options

I just wanted to find out if there is some way to disable the forced loading of the "What's New" page when Firefox updates. It would be better if this didn't open in a tab or browser window at all, similar to how apps like Discord display when the program has automatically updated. If that's not possible, maybe not opening the "What's New" tab as the first screen that the user interacts with would be less of a time draw.

Sometimes I just want to get to a site quickly and having to load the "What's New" page causes browser load/user interaction times to slow down.

I just wanted to find out if there is some way to disable the forced loading of the "What's New" page when Firefox updates. It would be better if this didn't open in a tab or browser window at all, similar to how apps like Discord display when the program has automatically updated. If that's not possible, maybe not opening the "What's New" tab as the first screen that the user interacts with would be less of a time draw. Sometimes I just want to get to a site quickly and having to load the "What's New" page causes browser load/user interaction times to slow down.

Alle antwurden (1)

zeroknight
zeroknight
more options

You can prevent anything opening after updates by going to about:config in the address bar and change browser.startup.homepage_override.mstone to ignore.