cancel
Showing results for 
Search instead for 
Did you mean: 

Difference between extensions.update.autoUpdateDefault and extensions.update.enabled

SOLVED
Highlighted
New Contributor

Difference between extensions.update.autoUpdateDefault and extensions.update.enabled

What is exactly the difference between these options? I have done a few tests but am not 100% sure. Currently I'm assuming extensions.update.enabled does only check for new versions of addons but it does not install them while extensions.update.autoUpdateDefault does only install addons if Firefox has already found a new version of them.

In this case setting only extensions.update.autoUpdateDefault to false would disable the automatic installing of addons and setting only extensions.update.enabled to false would disable the automatic searching for new addons which also implicitly disables the automatic installing of addons.

If my assumption is correct setting only extensions.update.enabled to false would be enough to disable any communication to an addon server.

1 ACCEPTED SOLUTION

Accepted Solutions
Senior Contributor

Re: Difference between extensions.update.autoUpdateDefault and extensions.update.enabled

Sworddragon said:

Currently I'm assuming extensions.update.enabled does only check for new versions of addons but it does not install them while extensions.update.autoUpdateDefault does only install addons if Firefox has already found a new version of them.

Your assumption seems to be confirmed in this Bugzilla thread from 2011 (please do not post in the thread, it is for Mozilla developers only)- https://bugzilla.mozilla.org/show_bug.cgi?id=701987

1 REPLY
Senior Contributor

Re: Difference between extensions.update.autoUpdateDefault and extensions.update.enabled

Sworddragon said:

Currently I'm assuming extensions.update.enabled does only check for new versions of addons but it does not install them while extensions.update.autoUpdateDefault does only install addons if Firefox has already found a new version of them.

Your assumption seems to be confirmed in this Bugzilla thread from 2011 (please do not post in the thread, it is for Mozilla developers only)- https://bugzilla.mozilla.org/show_bug.cgi?id=701987