Closed Bug 986306 Opened 10 years ago Closed 7 years ago

Add API to programmatically generate XPIProvider add-on sub-types

Categories

(Toolkit :: Add-ons Manager, defect)

Product:
Toolkit
Component:
Add-ons Manager
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: Unfocused, Unassigned)

Details

We seem to be needing to add new sub-types of add-ons to XPIProvider somewhat regularly. These are just normal XPI-based bootstrapped extensions, with slight behaviour differences - the behaviour differences seem to be clustered around a set of certain areas. Small things like look for a bootstrap script or use a built-in one instead, allow normal update mechanism or not, allow web install or not, etc.

And some of these would ideally not be implemented in Add-on Manager code, but rather with the module they're coming from. Take the experiments add-on type for instance - which from a code organisation standpoint would best be located in browser/experiments (which is app-specific!). But from an implementation standpoint, is far better being implemented as a subtype in XPIProvider.

Given what we've learned from adding sub-types so far, I think we can abstract out an API to provide a way to programatically generate sub-types at runtime. This would also allow add-ons to use this, and allow some nice (and much quicker) experimentation.
Fail.
Summary: Add API to programmatically generate a way to implement sub-types of add-ons from XPIProvider, rather than needing to modify XPIProvider each time → Add API to programmatically generate XPIProvider add-on sub-types
Component: Build Config → Add-ons Manager
Things have changed since this was first filed...
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.