Closed Bug 1485541 Opened 2 years ago Closed 2 years ago
Experimental APIs can't define lifecycle events
46 bytes, text/x-phabricator-request
|Details | Review|
https://firefox-source-docs.mozilla.org/toolkit/components/extensions/webextensions/lifecycle.html documents that APIs can define lifecycle events. However, attempts by an experimental API to define these events fails. The schema definition at https://searchfox.org/mozilla-central/rev/f2ac80ab7dbde5400a3400d463e07331194dec94/toolkit/components/extensions/schemas/experiments.json#105 only allows for a "startup" event. Even if we add the new events there, they never fire, because (IIUC), the experiment manager is a LazyAPIManager rather than an apiManager defined in ExtensionParent.jsm, which is where support for these events is wired up.
The problem with uninstall and update events is much larger: they require running code from an extension that is not active.
Comment on attachment 9006378 [details] Bug 1485541 Clarify documentation on extension lifecycle events Kris Maglione [:kmag] has approved the revision.
Attachment #9006378 - Flags: review+
https://hg.mozilla.org/integration/mozilla-inbound/rev/d6f84a0a8794302974c1706b33065e5d71629958 Bug 1485541 Clarify documentation on extension lifecycle events DONTBUILD r=kmag
Is manual testing required on this bug? If yes, please provide some STR and the proper extension(if required) or set the “qe-verify -“ flag. Thanks!
This patch was just a documentation update
Flags: needinfo?(aswan) → qe-verify-
You need to log in before you can comment on or make changes to this bug.