Closed Bug 842922 Opened 11 years ago Closed 10 years ago

Addon maxVersion is ignored by AMO for non-native extensions (type 2)

Categories

(addons.mozilla.org Graveyard :: Public Pages, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: haqer, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:18.0) Gecko/20100101 Firefox/18.0
Build ID: 20130104151925

Steps to reproduce:

Check out 2 examples:
1. https://addons.mozilla.org/en-US/firefox/addon/QIRIMTATARCA-til-destesi/versions/
2. https://addons.mozilla.org/en-US/thunderbird/addon/qirimtatarca-til-destesi-posta/versions/


Actual results:

a. A lot of version show " and later" instead of the maxVersion actually specified when the addon was submitted (the maxVersion wasn't changed by the developer after submittals).
b. Incompatible versions can be installed at will.


Expected results:

a. The maxVersion should match whatever the developer specifies.
b. Incompatible versions shouldn't be installable.
Another example:
3. https://addons.mozilla.org/en-US/firefox/addon/blend-in/versions/

P.S. All three examples have maxVersion assigned for each version, and in all cases the version is maxed at the release corresponding to the addon version (for the 3. examples maxVersion is sometimes addonVersion+1).
This issue is happening for type 2 addons (extensions). It is not happening for type 8 addons (lang packs).
Summary: Addon maxVersion is sometimes ignored by AMO → Addon maxVersion is ignored by AMO for extensions (type 2)
More specifically:
This issue is happening for non-native type 2 addons (extensions). It is not happening for type 8 addons (lang packs), and type 2 addons with binary components.
Summary: Addon maxVersion is ignored by AMO for extensions (type 2) → Addon maxVersion is ignored by AMO for non-native extensions (type 2)
Extensions default to compatible since Firefox 10 (https://blog.mozilla.org/addons/2012/01/05/default-compatibility-is-coming-and-your-help-is-needed/). 

If you want to limit your extension's compatibility, you need to set the strictCompatibility flag: https://developer.mozilla.org/en/Install_Manifests#strictCompatibility. AMO knows about this flag and handles it appropriately. See, for example: https://addons.mozilla.org/firefox/addon/click-to-play-manager/
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
FYI: I had to open bug 857431 as a follow-up to this issue.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Thanks for filing this.  Due to resource constraints we are closing bugs which we won't realistically be able to fix.  If you have a patch that applies to this bug please reopen.

For more info see http://micropipes.com/blog/2014/09/24/the-great-add-on-bug-triage/
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago10 years ago
Resolution: --- → WONTFIX
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.