Closed
Bug 682457
Opened 13 years ago
Closed 12 years ago
Standalone addon compatibility check should validate a range from maxVersion
Categories
(addons.mozilla.org Graveyard :: Developer Pages, defect)
addons.mozilla.org Graveyard
Developer Pages
Tracking
(Not tracked)
RESOLVED
WONTFIX
Q3 2011
People
(Reporter: kumar, Assigned: kumar)
Details
The standalone validator currently lets you choose your target app version from a dropdown. It should also parse the install.rdf (if it exists) and use the maxVersion to validate the full range between max and target.
This was supposed to be done in bug 668901, whoops.
This also requires a change to the validation results page so it can display a range of targeted app version results.
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → kumar.mcmillan
Target Milestone: --- → 6.2.3
Updated•13 years ago
|
Target Milestone: 6.2.3 → Q3 2011
Comment 1•12 years ago
|
||
I don't think this is necessary. If an add-on only targets a specific range of versions, we shouldn't show compatibility issues for versions outside of that range. Things like hotfix add-ons don't care about future versions, only the versions that they were built for. Validation always runs compat tests (during standalone and submission) for the range of versions that the add-on can be installed for.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Updated•9 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•