Closed
Bug 554083
Opened 15 years ago
Closed 15 years ago
FireFTP should be listed before "FireFTP button" in search results
Categories
(addons.mozilla.org Graveyard :: Search, defect)
addons.mozilla.org Graveyard
Search
Tracking
(Not tracked)
VERIFIED
FIXED
5.12
People
(Reporter: krupa.mozbugs, Assigned: davedash)
References
()
Details
steps to reproduce:
1.Go to https://preview.addons.mozilla.org/en-US/firefox/search?q=fireFTP&cat=all
expected result:
FireFTP should be listed before FireFTP button in search results
actual result:
FireFTP button is listed first
| Assignee | ||
Comment 1•15 years ago
|
||
So the weight is the same for both of these.
There's a few tricks we could do to try to boost this... I'll try them later possibly.
We can do a CRC32("name") and also search for the CRC32("query") and see if they match and if they match, nudge the result by one.
CCing James to see what he thinks.
Status: NEW → ASSIGNED
Comment 2•15 years ago
|
||
A heuristic for "what did the person really mean" might include weighting (in part) by popularity. Rather than dealing with extra CRCs (which are case sensitive and would add some extra juggling) I'd think about changing the sort mode to an expression and do something along the lines of "@weight + log(ADU)".
| Assignee | ||
Comment 3•15 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Target Milestone: --- → 5.12
Comment 4•15 years ago
|
||
Looks fixed in prod (5.11.9), to me: https://addons.mozilla.org/en-US/firefox/search/?q=fireFTP&cat=all
| Reporter | ||
Comment 5•15 years ago
|
||
verified at https://preview.addons.mozilla.org/en-US/firefox/search/?q=fireftp&cat=all&lver=any&pid=1&sort=&pp=20&lup=&advanced=
checked with Dave that we don't care(so much) about weights when it comes to personas(https://preview.addons.mozilla.org/en-US/firefox/search/?q=fireftp&cat=all&lver=any&pid=1&sort=&pp=20&lup=&advanced= )
Status: RESOLVED → VERIFIED
Updated•10 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
•