Updates page shown on Firefox

[greiner]

Environment

Windows 10
Firefox 59.0.2
Adblock Plus 3.0.3

How to reproduce

1. Install a version of Adblock Plus lower than 3.x
2. Update to version 3.x

Observed behaviour

New tab is opened showing updates page.

Expected behaviour

No new tab is opened.

Further information

Upon inspecting the code I noticed the following line in lib/adblockplus.js for the "info" module which explains why the updates page is shown:

exports.platform = "chromium";

Presumably, the purpose of this is to indicate that both Chromium and Gecko use a similar extension API but I'd argue that categorizing Firefox as "chromium" is misleading and that "webext" would be more accurate if our intention is to indicate that.

Furthermore, I noticed the following line in the same section which may or may not be related:

exports.addonName = "adblockpluschrome";

From what I can tell, this value should be "adblockplusfirefox" as defined ​in metadata.gecko which indicates that the wrong build was uploaded to AMO in which case I'd imagine there'd be further issues (e.g. wrong options page used on Firefox Mobile).

[kzar]

Update page popup for Firefox extension on Android

[kzar]

I originally posted this comment on #6599, but I'll duplicate it here for completeness:

I use Firefox (60.0) on Android (7.0) with the Adblock Plus extension installed on my phone (Moto G4 Plus) and this morning I saw the updates page popup! Needless to say it didn't look great, screenshot attached.

[sebastian]

Yep, as it seems the build for Chrome has been mistakenly uploaded to AMO.

[fhd]

I'll look into it.

[fhd]

Yup, that's what happened. I've re-released 3.0.3 as 3.0.4 and uploaded the XPI to AMO.

Some ideas on what we can do to avoid this issue in the future:

1. We copy the XPI to the working directory (currently it only ends up in the downloads repo, where I missed it).
2. We add a note to the release checklist that there's a separate build for Firefox (as opposed to Opera).

[sebastian]

It seems historically, the Firefox builds only end up in the downloads repository (but FWIW the old release check list for the legacy extension was more explicit about this). The reason that the Chrome/Opera builds end up in the local working directory is mostly because they differ from the version added to the downloads repository (i.e. the signature must be stripped, otherwise you cannot upload it to the CWS).

Anyway, I see how it can cause confusion (leading to a mess like this), to have one build in the local directory that is supposed to be uploaded to two of three websites, while the build supposed to be uploaded to AMO is hidden somewhere else. Therefore I just updated the release checklist template, in order to make it explicit which build has to be uploaded where.