Bugzilla

(In reply to Jorge Villalobos [:jorgev] from comment #6)
> Is there a good reason we treat `onInstalled` differently than Chrome?

We don't treat `onInstalled` differently from Chrome:

- When an installed extension (CRX file) is reloaded in Chrome (e.g. by granting incognito access), the `onInstalled` event is not fired.
 When an installed extension (XPI file) is reloaded in Firefox (e.g. by allowing private browsing access), the `onInstalled` event is not fired either.
- When an unpacked extension is reloaded in Chrome, `onInstalled` is fired with `reason=update`.
 When a temporary extension is reloaded in Firefox, `onInstalled` is fired with `reason=update` as well.

I filed a new bug for the disappeared context menu, as bug 1558336, which covers the second issue from comment 5.

The only remaing issue (the closed extension tabs) is expected behavior from a technical POV, but we were indeed receptive to the idea of improving the onboarding experience.

(In reply to Jorge Villalobos [:jorgev] from comment #6)
> Is there a good reason we treat `onInstalled` differently than Chrome?

We don't treat `onInstalled` differently from Chrome:

- When an installed extension (CRX file) is reloaded in Chrome (e.g. by granting incognito access), the `onInstalled` event is not fired.
 When an installed extension (XPI file) is reloaded in Firefox (e.g. by allowing private browsing access), the `onInstalled` event is not fired either.
- When an unpacked extension is reloaded in Chrome, `onInstalled` is fired with `reason=update`.
 When a temporary extension is reloaded in Firefox, `onInstalled` is fired with `reason=update` as well.

I filed a new bug for the disappeared context menu, as bug 1567467, which covers the second issue from comment 5.

The only remaing issue (the closed extension tabs) is expected behavior from a technical POV, but we were indeed receptive to the idea of improving the onboarding experience.