Closed
Bug 497677
Opened 16 years ago
Closed 15 years ago
AMO should display the latest compatible version of an add-on for given application
Categories
(addons.mozilla.org Graveyard :: Developer Pages, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 526077
People
(Reporter: rcampbell, Unassigned)
Details
Example:
We have Firebug 1.4b1 on AMO and it is listed as compatible with Firefox 3.5b4 - 3.5.*.
A user with Firefox 3.0.10 visits AMO looking for Firebug and is presented with Firebug 1.4b1 as the latest version. He should instead see Version 1.3.3 of Firebug as the top-most extension for that version, possibly with some wordage below the install button saying that there is a newer version available for a later version of Firefox.
Alternatively, a mechanism to mark an extension as Beta so it doesn't show up for all users and is presented in a smaller, less obvious way.
Comment 1•16 years ago
|
||
Uhm, isn't that already the case? It should detect that you are using a version of Firefox not compatible with the latest extension version and tell you that there may be an older version available. When you click the link, it'll take you to the "all version" page which will suggest the latest version compatible with your version of Firefox.
Reporter | ||
Comment 2•16 years ago
|
||
that's my point. You have to go through a click or two to get to the most-recent, available version. I'd prefer to see the most-recent compatible version presented to the user and the little box underneath say, "if you upgrade your browser, you can get a new version of this add-on".
Comment 3•16 years ago
|
||
Release channels is something we're looking at soon and which will fix this bug.
Reporter | ||
Comment 4•16 years ago
|
||
feel free to add that bug as blocking this one.
Comment 5•15 years ago
|
||
the beta release channel is coming next week from bug 526077
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Assignee | ||
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
•