So that an add-on can uninstall another add-on, which will support bug 1280233.
Priority: -- → P4
Whiteboard: [management] → [management] triaged
Can any WebExtension do this, or is this a one-off for TestPilot? And when I do install TestPilot, what's to prevent it from uninstalling e.g. TabCenter, which I've already installed? It would be more generally useful to let a WebExtension specify dependencies on other WEs, and implement a dependency resolution system instead. Useful to TestPilot, useful to other extensions with add-on dependencies , useful for extensions to share main-process APIs among themselves .  https://www.google.com/search?q=This+add-on+requires+the+following+add-ons+to+work+properly+site%3Aaddons.mozilla.org  https://discourse.mozilla-community.org/t/proposal-native-js-to-embrace-extend-the-webextensions-api/3457
Note that Chrome already allows this, so we'd probably have to implement this for Chrome parity: https://developer.chrome.com/extensions/management#method-uninstall I personally am wary about building out dependency management in WebExtensions, I'm not sure of the value. However probably the best place to put that as a seperate bug would be as a dependency of bug 1263011. See also bug 1223642.
We will not be implementing this until we are presented with a valid use case from add-on developers.
No longer blocks: 1282979
Priority: P4 → P5
Component: WebExtensions: Untriaged → WebExtensions: General
Most of the add-on management on testpilot.firefox.com can be done on the website itself. The only case I can think of in use right now where Test Pilot uninstalls an existing add-on is when Test Pilot itself is uninstalled, it takes all the active experiments with it. Seen from a user point of view, this is "Leaving the Test Pilot program" all in one swoop. Converting Test Pilot to a web extension is likely going to become a 2017 goal for the Test Pilot team so I'd like to reopen discussion on this.
(In reply to Bob Silverberg [:bsilverberg] from comment #3) > We will not be implementing this until we are presented with a valid use > case from add-on developers. Add-on manager in sidebar: all in one sidebar provides this. Add-on manager in panel: https://addons.mozilla.org/en-US/firefox/addon/simple-add-on-manager/
webextensions: --- → ?
(In reply to Tim Nguyen :ntim from comment #5) > (In reply to Bob Silverberg [:bsilverberg] from comment #3) > > We will not be implementing this until we are presented with a valid use > > case from add-on developers. > > Add-on manager in sidebar: all in one sidebar provides this. > > Add-on manager in panel: > https://addons.mozilla.org/en-US/firefox/addon/simple-add-on-manager/ That's a cute addon certainly. However, the functionality already exists in Firefox, and it only has 615 users. Through 57 we have to be selective in where we apply our resources, I don't feel like this is a big enough use case.
(In reply to Wil Clouser [:clouserw] from comment #4) > Converting Test Pilot to a web extension is likely going to become a 2017 > goal for the Test Pilot team so I'd like to reopen discussion on this. Is this the only blocker on that? Is anyone going to generate a list of issues (real soon) that would need to be addressed for test pilot?
Since the related bug 1280237 was WONTFIXed, should this bug also be closed?
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1269288
You need to log in before you can comment on or make changes to this bug.