1112788 - Add "e10s" as an artificial Firefox version in order to use it for compatibility overrides

Status: RESOLVED WONTFIX

(addons.mozilla.org Graveyard :: Compatibility Tools, defect)

Description

[Jorge Villalobos [:jorgev] (he/him)]

We want to flag add-ons as incompatible with e10s, and it seems like the easiest solution is to introduce "e10s" as a valid Firefox version so it can be used in the compatibility override tool. This will also require some work on the Firefox side in order to support this version.

I'll start by staging this change to make sure there isn't unexpected breakage.

Comment 1

[Jorge Villalobos [:jorgev] (he/him)]

Okay, so I added "e10s" as a valid version number on staging (addons-dev.allizom.org). Then I modified a compatibility override so the Firefox version range is e10s - e10s. The add-on is gTranslator: https://addons-dev.allizom.org/addon/gtranslator/. I noticed a couple of things:

* The compatibility override tool takes free-form version numbers, so we can probably do this without adding e10s as a valid version number. The advantage of not adding it is that it won't show up on version number dropdowns across the site, which could confuse some devs.

* Our version comparison algorithm places e10s below any numerical versions (so e10s < 0). This is why I set the Firefox version range to e10s - e10s for the gTranslator test. If set to e10s - *, then it would effectively flag the add-on as incompatible with all Firefox versions.

So, on the Firefox side we would need to change the Add-on Manager code that reads the overrides, in order to support the special e10s - e10s range and apply it when e10s is enabled in Firefox.

Comment 2

[Chris Peterson [:cpeterson]]

Adding this AMO bug to the list of e10s bugs we're tracking.

Comment 3

[Adrian Florinescu [:aflorinescu]]

As per Chris Peterson [:cpeterson] feedback, setting status as Resolved:Won't Fix.