Closed Bug 660107 Opened 13 years ago Closed 11 years ago

First startup after automatic installation gets APP_STARTUP instead of ADDON_INSTALL

Categories

(Toolkit :: Add-ons Manager, defect)

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

Tracking

()

Status:
RESOLVED DUPLICATE of bug 854937

People

(Reporter: Mardak, Unassigned)

References

Details

For a boostrapped add-on that gets automatically installed (perhaps by distribution or upgrade(?)), its startup gets called with APP_STARTUP.

That's arguably correct, except now bootstrapped add-ons can't rely on ADDON_INSTALL for startup reason, which is what they normally get if the user manually installs the add-on.

Workaround: Track ADDON_INSTALL from install() and check it from startup().
Is this something that can be fixed Dave?
Flags: needinfo?(dtownsend+bugmail)
Not only can we fix it, but we already have
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(dtownsend+bugmail)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.