Closed
Bug 970373
Opened 11 years ago
Closed 5 years ago
Better search results for literal keywords and incomplete keywords
Categories
(developer.mozilla.org Graveyard :: Search, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: sole, Unassigned)
Details
(Whiteboard: [specification][type:feature][search-quality])
What problems would this solve?
===============================
Getting better search results when looking for a keyword (or part of it)
Who would use this?
===================
Developers, all the time
What would users see?
=====================
Better results rather than some other page that might have something to do with the topic but not directly
What would users do? What would happen as a result?
===================================================
They would search keywords and would get the results they expect. For example now if I search "installs_allowed" I get four other results before the app manifest page, which is the one which should be the authority here.
Looks like the underscore has been removed and we're looking for "installs allowed" which is pretty different.
Likewise if I look for "requestAnimation" I just get ONE result on something that is relatively tangential to the topic-I should get requestAnimationFrame results too, and in the first position because "requestAnimation" is in the title.
Is there anything else we should know?
======================================
Updated•11 years ago
|
Component: General → Site search
Updated•11 years ago
|
Severity: normal → minor
Whiteboard: [specification][type:feature] → [specification][type:feature][search-quality]
Comment 1•5 years ago
|
||
MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Updated•5 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•