Bug 1485541 Clarify documentation on extension lifecycle events DONTBUILD r=kmag

Differential Revision: https://phabricator.services.mozilla.com/D4984

--HG--
extra : rebase_source : a1affdb128957473e0b98441f0cf715cdbddad03
extra : amend_source : fe28c8bb0f8592e4b0df967a5f849b7686529b4d
This commit is contained in:
Andrew Swan 2018-09-04 14:04:05 -07:00
Родитель 5b31094f82
Коммит bf0e0ade45
1 изменённых файлов: 10 добавлений и 0 удалений

Просмотреть файл

@ -32,6 +32,9 @@ the ``onManifestEntry()`` method for the API is no longer called,
but an API can examine the new manifest after an update to detect that
the key has been removed.
Handling lifecycle events
-------------------------
To be notified of update and uninstall events, an extension lists these
events in the API manifest:
@ -47,4 +50,11 @@ If these properties are present, the ``onUpdate()`` and ``onUninstall()``
methods will be called for the relevant ``ExtensionAPI`` instances when
an extension that uses the API is updated or uninstalled.
Note that these events can be triggered on extensions that are inactive.
For that reason, these events can only be handled by extension APIs that
are built into the browser. Or, in other words, these events cannot be
handled by APIs that are implemented in WebExtension experiments. If the
implementation of an API relies on these events for corectness, the API
must be built into the browser and not delievered via an experiment.
.. Should we even document onStartup()? I think no...