1178127 - Add-on disabled by version with strictCompatibility is "not verified for use"

Status: RESOLVED DUPLICATE of bug 1195034

(Toolkit :: Add-ons Manager, defect)

Description

[Simon Kornblith]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:39.0) Gecko/20100101 Firefox/39.0
Build ID: 20150611135623

Steps to reproduce:

Create a new extension whose manifest specifies <em:strictCompatibility>true</em:strictCompatibility> and requires a Firefox version older than the currently installed version


Actual results:

Under Firefox Developer Edition 40, the add-on manager shows "<EXTENSION NAME> could not be verified for use in Firefox Developer Edition and has been disabled." Clicking "More Information" opens a new tab leading to https://support.mozilla.org/en-US/kb/add-ons-signing-firefox?as=u&utm_source=inproduct.

This seems wrong, since the reason the add-on has been disabled has nothing to do with add-on signing. A user encountering this message would likely have no insight into why the add-on was disabled and how to correct this issue.


Expected results:

Under Firefox 39, the add-on manager shows "<EXTENSION NAME> is incompatible with Firefox 39.0"

Comment 1

[Dave Townsend [:mossop]]

Only really going to be an issue if users have changed the default setting once bug 1167652 is fixed.

Comment 2

[Dave Townsend [:mossop]]

[Tracking Requested - why for this release]:

Some slightly confusing messaging here.

Comment 3

[Ritu Kothari (:ritu) (Inactive, please n-i to RyanVM, jcristau, or pascal)]

While this is a valid bug, I don't think it is severe enough to warrant a fix in FF 40. Approving for FF41 and FF42.

Comment 4

[Liz Henry (:lizzard) (relman/hg->git project)]

Is this something you would confirm is an issue? Though we've marked this as affected, I noticed no one confirmed the bug. It seems pretty safe to do so but I'm double checking. 

Can you help find an owner for this bug? Thanks.

Comment 5

[Dave Townsend [:mossop]]

Definitely an issue and I'd take a fix if someone provided one, but I don't think it is important enough to assign an engineer to at this point.

Comment 6

[Ritu Kothari (:ritu) (Inactive, please n-i to RyanVM, jcristau, or pascal)]

I do not think this is a release blocker for FF41. Given that we do not have an owner yet, I doubt this will get fixed for FF41.

Comment 7

[Dave Townsend [:mossop]]

Oh I was looking for this bug. We fixed it already.