Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Can I stop Firefox from opening "What's new" page on upgrade?

  • 3 antwoorden
  • 1 heeft dit probleem
  • 18 weergaven
  • Laatste antwoord van TyDraniu

more options

Firefox install: Linux 64bit from Mozilla web (NOT using distribution package) Current version: 68.0 (up to date) Upgrades: [X] Automatically install updates (recommended)

Whenever Firefox upgrades (on new major version only?), it opens page with news about the version (https://www.mozilla.org/en-US/firefox/68.0/whatsnew/?oldversion=67.0.4) on startup. Can this be stopped? How?

Firefox install: Linux 64bit from Mozilla web (NOT using distribution package) Current version: 68.0 (up to date) Upgrades: [X] Automatically install updates (recommended) Whenever Firefox upgrades (on new major version only?), it opens page with news about the version (https://www.mozilla.org/en-US/firefox/68.0/whatsnew/?oldversion=67.0.4) on startup. Can this be stopped? How?

Alle antwoorden (3)

more options

hello Ravise, you can try the folloing tweak to change this behaviour: enter about:config into the address bar, search for the preference named browser.startup.homepage_override.mstone & change its value to ignore.

more options

philipp said

hello Ravise, you can try the folloing tweak to change this behaviour: enter about:config into the address bar, search for the preference named browser.startup.homepage_override.mstone & change its value to ignore.

Thanks for swift reply! I've followed your advice. Unless there's some way to test that artificially, I'll have to wait for next major release to confirm whether it's working.

more options

Somewhere around version 70, the opening of the "What's new" page will be removed, in favor of a new toolbar item showing up. See bug 1561009.