Closed
Bug 1065320
Opened 10 years ago
Closed 4 years ago
MDN search: show HTML results before XUL/XPCom results
Categories
(developer.mozilla.org Graveyard :: Search, defect)
developer.mozilla.org Graveyard
Search
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: paul, Unassigned)
References
Details
Mozilla internal documentation should never show-up by default. For example: https://developer.mozilla.org/en-US/search?q=filter This should show CSS, HTML and JS results, not /Mozilla/Tech/XUL/Template_Guide/Filtering. Maybe a checkbox "includes mozilla internal documentation", that is off by default.
Comment 1•10 years ago
|
||
I don't agree with this. However, I do think that if you have two pages that have the same title, but one is in the /Web subtree and the other is not, the one under /Web should be listed first. That would ensure that, for instance, HTML elements with the same name as a XUL element would be listed first.j
Reporter | ||
Comment 2•10 years ago
|
||
(In reply to Eric Shepherd [:sheppy] from comment #1) > I don't agree with this. However, I do think that if you have two pages that > have the same title, but one is in the /Web subtree and the other is not, > the one under /Web should be listed first. That would ensure that, for > instance, HTML elements with the same name as a XUL element would be listed > first. That would work for me.
Summary: MDN search: hide XUL/XPCom results by default → MDN search: show HTML results before XUL/XPCom results
Updated•10 years ago
|
Assignee: eshepherd → nobody
Component: General → Search
OS: Linux → All
Product: Developer Documentation → Mozilla Developer Network
Hardware: x86_64 → All
Comment 3•4 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: 4 years ago
Resolution: --- → WONTFIX
Updated•4 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
•