Label "recommended" extensions in addons manager search results

RESOLVED WONTFIX

Status

()

Toolkit
Add-ons Manager
--
enhancement
RESOLVED WONTFIX
10 years ago
2 months ago

People

(Reporter: tchung, Unassigned)

Tracking

({uiwanted})

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9pre) Gecko/2008051304 Minefield/3.0pre
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9pre) Gecko/2008051304 Minefield/3.0pre

it would be great if we can distinguish the "recommended" extensions in the search results of addons manager.   We currently do that on AMO, could we design something like that also that sticks out?   We already have a list of recommended items, how hard would it be to do that?  

People always love when someone recommends something, especially our extension authors.

See screenshot.  

Reproducible: Always

Steps to Reproduce:
1. Install nightly
2. Open addons manager > Get addons
3. Search for an extension that is considered "recommended" by AMO.  (eg. Interclue)
4. Verify search results window dont have a way to call out that extension as "recommended".  
Actual Results:  
No "recommended" label for extensions in search results

Expected Results:  
"Recommended" Label someplace
(Reporter)

Comment 1

10 years ago
Created attachment 320833 [details]
No Recommended Label screenshot
This is a good idea I think though right now it is not possible. I have filed bug 433673 to add the necesary information to the API calls.
Severity: normal → enhancement
Depends on: 433673
(Assignee)

Updated

10 years ago
Product: Firefox → Toolkit
That's about the old UI which has been completely replaced. But we still don't call out recommended add-ons for searches.
Keywords: uiwanted

Comment 4

2 months ago
The search is being replaced with AMO in bug 1263313.
Status: NEW → RESOLVED
Last Resolved: 2 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.