Closed Bug 702280 Opened 10 years ago Closed 5 years ago

extensions.disableScopes cannot be updated via distribution.ini mechanism

Categories

(Toolkit :: Add-ons Manager, defect)

8 Branch
x86
Windows 7
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: mkaply, Unassigned)

Details

The recommended way for enterprises to set extensions.diableScopes for their internal use is to use distribution.ini.

Something like this in distribution/distribution.ini

[Global]
id=Kaply Consulting
version=1.0
about=

[Preferences]
extensions.autoDisableScopes=0 

This does not work.

Although autoDisableScopes is picked up in about:config, it is not read during startup, so add-ons continue to be disabled.

The only workaround is to set the value in a defaults/prefs/prefs.js file instead.
This is a timing issue, where distribution.ini isn't getting read before the addons manager is opened. We've had related bugs in the past, adding Thunder for comment, as I believe we'd have to make a change in the aom module to check for the scope to make this work.
Actually, they should use autoconfig for this.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.