1847186 - Enable the `mozAddonManager` web API on Fenix Nightly builds

Status: VERIFIED FIXED

(Fenix :: WebExtensions, task, P1)

Description

[William Durand [:willdurand]]

Before we can fix Bug 1847172, let's enable the web API on Nightly builds first.

Comment 1

[BMO Github Automation]

Attachment: [mozilla-mobile/firefox-android] Bug 1847186 - Enable the `mozAddonManager` web API on Fenix Nightly builds (#3116)

Comment 2

[BMO Github Automation]

Authored by https://github.com/willdurand
https://github.com/mozilla-mobile/firefox-android/commit/bb16d29ce9df64bb366b006611db74c9a45c0d78
[main] Bug 1847186 - Enable the mozAddonManager web API on Fenix Nightly builds

Comment 3

[Delia Pop]

Hi, William,
Is QA verification needed for this issue? If so, could you please provide some steps to reproduce or testing scenarios? Thanks!

Comment 4

[William Durand [:willdurand]]

Hi, the scenarios I could think of are the following:

1. in Fenix Nightly, install an add-on from AMO: a notable difference is that the "install" button on AMO is now interactive, i.e. there is an animation when the install starts, and the "Install" button is updated to "Remove" when the add-on is installed. Removing the extension from AMO should work. Similarly, it should be possible to "enable" an add-on from AMO when that add-on has been disabled from the Fenix Add-ons Manager.

2. in Fenix Nightly, installing an add-on from the Fenix Add-ons Manager should work as before, and the install flow from AMO AND the Fenix Add-ons Manager should be the same (same dialogs, same information)

3. With a custom AMO collection configured in Fenix Nightly that contains one of the "officially supported" add-ons (e.g. uBlock Origin), installing this add-on from AMO should work. Installing any other add-ons not in the custom collection from AMO should show an error message indicating that the add-on is not supported (see also: Bug 1847179).

Thanks!

Comment 5

[Delia Pop]

Thank you, I verified all the scenarios and no issues were observed. I'll mark this ticket verified as fixed in latest Nightly 118.0a1 from 08/10 with Samsung Galaxy A53 5G (Android 13).