1700797 - runtime.onInstalled Does not run if the extension is updated while it is disabled

Status: NEW

(WebExtensions :: General, defect, P3)

Description

[filipe.panni]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:87.0) Gecko/20100101 Firefox/87.0

Steps to reproduce:

1 - Install an old version of an extension
2 - Disable the extension
3 - Update your extensions to the latest version
4 - Enable the extension again

Actual results:

The listeners of "runtime.onInstalled" will not be called when activating the extension

Expected results:

1 - The extension should not be updated if it was disabled
2 - Or when you activate the extension, the "runtime.onInstalled" listeners should be called.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'WebExtensions::Untriaged' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 2

[Alex Cornestean]

Hello,

I reproduced the issue on the latest Nightly (89.0a1/20210325161138), Beta (88.0b3/20210325185929) and Release (87.0/20210318103112) under Windows 10 x64 and Ubuntu 16.04 LTS.

Performing the actions mentioned in the STR, revealed indeed that add-ons can be updated while disabled and that the web console does not log the “onInstalled” event when enabling the add-on post update. The “onInstalled” event is triggered when initially installing the add-on and after updating it, but not when re-enabling the add-on. For further details, see the attached screenshot.

Comment 3

[Alex Cornestean]

Attachment: 2021-03-26_10h25_41.png

Comment 4

[Rob Wu [:robwu]]

Chrome seems to have the same behavior - https://bugs.chromium.org/p/chromium/issues/detail?id=388231

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

The component has been changed since the backlog priority was decided, so we're resetting it.
For more information, please visit auto_nag documentation.

Comment 8

[Rob Wu [:robwu]]

Bug 1826825 and bug 1906670 include test cases and more context on this issue.