Closed Bug 521593 Opened 15 years ago Closed 15 years ago

Experimental addon shows better keyword match than non-experimental addons

Categories

(addons.mozilla.org Graveyard :: Public Pages, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: callmejoe007, Assigned: davedash)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/532.0 (KHTML, like Gecko) Chrome/3.0.195.25 Safari/532.0 Build Identifier: all major browsers, IE 7, chrome or firefox I am browsing the Mozilla addons and I am witnessing some weird behavior. For example, when I search for download using the default keyword match (see attached image) https://addons.mozilla.org/en-US/firefox/search?q=toolbar&cat=all Below are the orders of the addons first four addons, 1. DNSQueries.com Toolbar ==>Why is this one first? this one has no rating, only 186 weekly downloads, matches no more keywords than #3 or #4 or #5. 2. DuVar.Tv ToolBar ==>this is experimental addon, why is it 2nd? 3. Image Toolbar ==>ok 4. Text size toolbar ==>ok Questions 1. Why is #1 & #2 where they are, they are no more relevant than #3 or #4. 2. Should experimental addons be before approved addons? isn't that a security risk? 3. How is keyword ranking calculated? educate me so that I don't stay mad at the search results? :) Thanks Reproducible: Always Steps to Reproduce: 1. Go to https://addons.mozilla.org/en-US/firefox/search?q=toolbar&cat=all and look at the listing. Actual Results: Experimental addons which are no more relevant are ranked higher than approved addons Expected Results: Approved addons should have better keyword match than Experimental, if relevance is the same
Assignee: nobody → dd
The AMO search was recently rewritten, and this issue seems fixed now. Please reopen if you still see it.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.