Add ability to manage other addons - list/install/uninstall/enable/disable

NEW
Unassigned

Status

defect
P5
normal
3 years ago
16 days ago

People

(Reporter: yuki, Unassigned)

Tracking

(Blocks 1 bug, {dev-doc-needed})

Trunk
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [design-decision-approved]triaged)

Reporter

Description

3 years ago
For enterprise use, the system administrator wants to manage addons via MCD (Mission Control Desktop) mechansim. For example: activate "dangerous" versions of other addons even if they are blocked by Mozilla. Currently it is possible with addons using AddonManager.jsm, however, after XUL is ended we need something to alter it.

Add-on hotfix mechanism https://wiki.mozilla.org/Features/Desktop/Add-on_hotfix and custom update manifest seems similar to this purpose, however, it is not guaranteed that it is executed on the startup immediately.

Updated

3 years ago
Whiteboard: [design-decision-needed]triaged
Reporter

Updated

3 years ago
Summary: Add ability to manage other addons - install/uninstall/enable/disable → Add ability to manage other addons - list/install/uninstall/enable/disable

Comment 1

3 years ago
Just a note that the ability to list all add-ons and uninstall them is covered in Chrome as well by the management API: https://developer.chrome.com/extensions/management. It does not allow you to install, enable or disable however.

This would also need permissions to be implemented.
Depends on: 1197420
Reporter

Comment 2

3 years ago
Thank you for pointing! Currently there seems to be no existing bug for "chrome.management", except the bug 1220136 about self-uninstallation. Should I separate this bug for two steps: 1) implementing "chrome.management" compatible to Google Chrome and 2) extending it with new permissions and new methods to enable/disable addons?

Comment 3

3 years ago
There's a few bugs on management: http://arewewebextensionsyet.com/#management, feel free to file any other. Please give them the [management] whiteboard tag.

Needless to say we should have permissions that prompt the user around these APIs.

Also we should approach install carefully, it should only be possible to install another signed WebExtension add-on for example, otherwise we've got a simple escape out of the sandbox.
Whiteboard: [design-decision-needed]triaged → [design-decision-approved]triaged

Updated

2 years ago
Duplicate of this bug: 1280236

Comment 5

2 years ago
A first release of this should be behind bug 1280235. Anything else would need to pass a security review.
Depends on: 1280235

Updated

2 years ago
Priority: -- → P5

Updated

11 months ago
Product: Toolkit → WebExtensions
Bulk move of bugs per https://bugzilla.mozilla.org/show_bug.cgi?id=1483958
Component: Untriaged → General
You need to log in before you can comment on or make changes to this bug.