Closed Bug 666437 Opened 9 years ago Closed 9 years ago

Allow extensions installed from certain locations to be disabled by default

Categories

(Toolkit :: Add-ons Manager, enhancement)

enhancement
Not set
normal

Tracking

()

VERIFIED FIXED
mozilla7

People

(Reporter: mossop, Assigned: mossop)

References

Details

(Keywords: dev-doc-complete, verified-aurora, verified-beta, Whiteboard: [qa!])

Attachments

(1 file)

To support bug 476430 we want to be able to mark certain install locations as installing their add-ons disabled by default.
Attached patch patch rev 1Splinter Review
This adds the pref extensions.autoDisableScopes. By default it isn't set to anything so all add-ons install enabled as normal.
Attachment #541226 - Flags: review?(robert.bugzilla)
Comment on attachment 541226 [details] [diff] [review]
patch rev 1

>diff --git a/toolkit/mozapps/extensions/test/xpcshell/test_startup.js b/toolkit/mozapps/extensions/test/xpcshell/test_startup.js
>--- a/toolkit/mozapps/extensions/test/xpcshell/test_startup.js
>+++ b/toolkit/mozapps/extensions/test/xpcshell/test_startup.js
>...
>+}
>\ No newline at end of file
nit
Attachment #541226 - Flags: review?(robert.bugzilla) → review+
Landed: http://hg.mozilla.org/mozilla-central/rev/25b6b9df083e
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: in-testsuite+
Flags: in-litmus-
Resolution: --- → FIXED
Target Milestone: --- → mozilla7
Dave, would that require devdoc or userdoc needed?
Yeah it's probably worth documenting this for other application's that want to use it
Keywords: dev-doc-needed
Setting resolution to Verified Fixed on 
Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20100101 Firefox/8.0 beta 6 build 2.
Mozilla/5.0 (Windows NT 6.1; rv:9.0a2) Gecko/20111102 Firefox/9.0a2
Mozilla/5.0 (Windows NT 6.1; rv:10.0a1) Gecko/20111031 Firefox/10.0a1
also on Ubuntu, MacOS X and WinXP

The extention is disabled at Firefox startup and the warning appears every time.
Also, the pref extensions.autoDisableScopes is present.
Status: RESOLVED → VERIFIED
Whiteboard: [qa!]
You need to log in before you can comment on or make changes to this bug.