Closed
Bug 273256
Opened 20 years ago
Closed 20 years ago
minVer should not be editable
Categories
(addons.mozilla.org Graveyard :: Developer Pages, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
1.0
People
(Reporter: Bugzilla-alanjstrBugs, Assigned: wolf)
Details
The minVer of a theme or extension should not be editable. The web service will not check against it. The application probably will not, either. The maxVer should remain editable, obviously.
| Assignee | ||
Comment 1•20 years ago
|
||
Having an editable minVer is beneficial to the Update website, it allows authors to fix their listings to be more accurate than the install.rdf if need be, which reduces the # of users who'd hit bugs or errors in the extension/theme with that version, even though it was intended to be compatible. It's unexpected behavior to have the MaxVer editable while the MinVer isn't. Sure, if somebody extends minVer below the install.rdf value, it won't work (Firefox's code path for that may or may not verify both parts of the TargetApplication arc, I haven't seen anything that says which for sure), but Firefox has an error message that's human readable for that. We're not particularly reliable about the information for older versions at this point anyway, we don't verify minAppVer compatibility, would you want to be the editor responsible for doing that to justify taking the control of minAppVer away from the authors? Seems more reasonable to me to leave it editable and let them adjust it as needed over time. Leaving the control, as we're giving it with maxAppVer, with the authors. We can deal with individual complaints of items that end up with bad values on a case-by-case basis.
Status: NEW → RESOLVED
Closed: 20 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
•