-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sort add-ons by newest add-ons #11129
Comments
Good idea, and the date of creation / update should be always visible (near the addon name) in all places where the addons are visible (search / listing / addon infos pages etc.. ). |
This issue did never got an label, but most other issues. Was it overlooked? ;-) |
This should be fixed to make it possible for people keep their add-on collections up to date. |
Here's why I don't think we should do this:
|
Sounds like this is not a feature that should be surfaced in the UI of the site. As @jvillalobos mentioned: it's a good candidate for a community-supported feature using the API, and as @cadeyrn mentioned it is possible to produce even on the site by changing the URL for the users who really desire the feature. Given the limited space for UI we have and our aim to reduce complexity, I'm gonna close this one. |
"Last updated" sorts add-ons by the date the last version was uploaded, IIRC. This means you get a mix of the newest add-ons and the add-ons that had new versions recently uploaded. |
This comment has been minimized.
This comment has been minimized.
Here's my little Friday afternoon project: https://addons.mozilla.org/addon/latest-on-amo/ Issues and patches welcome. |
I didn't mean the latest version release, I meant that I want to be able to sort add-ons by the release date of the first version. Example for the three most popular extensions would look like this:
|
Shouldn't this issue be re-opened (see my previous comment)? |
In my opinion as opener of this issue, yes, it should be reopened. But it's not my decision…
That's not true at all, it's a very different use case…
Seeing updated but old add-ons if you're interested in new add-ons, that's noisy.
On desktop AND mobile it's in a dropdown with only a few items. There is really no space issue.
I can't confirm that. I have a few Mozilla related projects like my not that small blog and I am also the administrator of the German speaking support Forum of Firefox so German speaking people often ask me or in one of my projects. There were more requests for this feature from simple users which are no active community members. These are users interested in the newest add-ons, they want discover new add-ons. I don't see how this use case should correlate with community engangement. |
Search Tools can be sorted by Created. But not add-ons. |
@cadeyrn you probably figured this out long ago but for convenience:
For me the redirects are to Where
– appears to be pre-selected and will not perform the sort, when required. It becomes necessary to select a different sort order, then (again) select Relevanz HTH Postscript: for new extensions that are not monitored by Mozilla, it is particularly important to promote awareness of risks https://support.mozilla.org/en-US/kb/recommended-extensions-program#w_what-are-the-risks-of-installing-non-recommended-extensions | https://support.mozilla.org/de/kb/programm-fur-empfohlene-erweiterungen#w_welche-risiken-bestehen-bei-der-installation-von-nicht-empfohlenen-erweiterungen and (from within that article) tips for assessing the safety of an extension. |
In the new design in the search results the option is missing to sort the add-ons by the newest. It seems to be still possible with the URL parameter sort=created but it should be added to the dropdown. I think it's a very nice option to discover new add-ons. There was also already a request in the German speaking Firefox forum where this option in the new design is.
It's maybe related to #2026 but I opened a separate ticket because the other ticket has the focus on the option to sort by name and this is a different use case (and so maybe there will be a different decision).
The text was updated successfully, but these errors were encountered: