Closed
Bug 989050
Opened 12 years ago
Closed 6 years ago
Add a "not" operator to the advanced search capability
Categories
(developer.mozilla.org Graveyard :: General, enhancement)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: sheppy, Unassigned)
Details
(Whiteboard: [specification][type:feature])
What problems would this solve?
===============================
The advanced search capability (https://developer.mozilla.org/en-US/docs/MDN/User_guide/Advanced_search) having a "not" operator would let us do things like find pages that do not currently have an SEO summary set by using a term like "css_classname=!seoSummary".
Who would use this?
===================
Users trying to make specific types of tweaks to content, such as adding SEO summaries to pages or looking for pages that are tagged X but not NeedsTechnicalReview, or something.
What would users see?
=====================
No UX changes.
What would users do? What would happen as a result?
===================================================
Search would otherwise work the same.
Is there anything else we should know?
======================================
Comment 1•12 years ago
|
||
Perhaps we should take a CSS selector as an argument instead. CSS already has :not() and many other useful selectors (child, direct descendent, sibling, etc., etc., etc.) that, if later needed, would become burdensome to support manually through new URL parameters.
Severity: normal → enhancement
Comment 2•6 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: 6 years ago
Resolution: --- → WONTFIX
Updated•6 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
•