Closed
Bug 1262543
Opened 8 years ago
Closed 4 years ago
Offer ability to remember user's preferred search filters
Categories
(developer.mozilla.org Graveyard :: Search, enhancement)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: sheppy, Unassigned)
References
Details
(Keywords: in-triage, Whiteboard: [specification][type:change])
What feature should be changed? Please provide the URL of the feature if possible. ================================================================================== Different developers have different search requirements. Add-on devs need add-ons enabled by default in search filters. Firefox developers need XPCOM enabled. And so forth. We need a way for users to set their default search filters; requiring them to manually adjust them for every. single. search. is just cruel. What problems would this solve? =============================== Ease of use. Plus it will keep our users from going insane. Who would use this? =================== All users who do search and don't want to go insane. What would users see? ===================== Depends on implementation. Either we remember the last-used filters automatically, or offer a "use as default" button. What would users do? What would happen as a result? =================================================== Avoid searches that don't make sense by remembering their needed filters. Is there anything else we should know? ======================================
Comment 1•8 years ago
|
||
Technically possible, could be stored in local storage as needed. A bookmark should work as an interim solution.
See Also: → 1261274
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
•