Filter reset that clears unrelated search

Problem Context

• The result set combines keyword search, filter criteria, sort, scope, saved search, saved filter, pagination, view density, or layout state.
• The UI offers Clear filters, Reset, Clear all, Start over, chip removal, mobile drawer reset, no-results recovery, or saved-filter apply actions.
• Users expect a filter reset to widen results by removing constraints, not to destroy the query or saved context that defines the result universe.
• The page may use batch filter drafts, applied filter chips, saved presets, URL parameters, search history, or mobile drawers that make state ownership hard to see.

Selection Rules

• Flag this anti-pattern when a filter reset clears or changes query text, submitted search, search scope, saved search identity, search history, sort order, page size, view mode, selected rows, or route context that is not visibly part of the filters.
• Use Clear filters for user-applied filter criteria only.
• Use Clear search or Clear query when the action removes search text or submitted search context.
• Use Clear search and filters, Reset all, or Start over only when the label names the broader effect and the UI lists the affected state.
• Use chip removal for one applied criterion and clear-all chips for the filter chip group, preserving query, sort, scope, and view state.
• Use saved filter when only reusable filter criteria are applied; preserve query and sort unless the preset explicitly stores them.
• Use saved search when query text, filters, sort, scope, and alert subscriptions are intentionally bundled into a saved object.
• In no-results recovery, offer scoped loosening actions before broad reset.
• In batch filter panels, distinguish Reset draft from Clear applied filters.
• If broad reset is destructive or hard to reconstruct, provide undo, confirmation, or a visible before/after state list.

Required States

• Default state with visible query, filters, sort, scope, and result count separated by ownership.
• Clear one filter state that removes only one criterion and preserves query and sort.
• Clear all filters state that removes all filter criteria and keeps the submitted query.
• Clear search state that removes query text without pretending it is a filter reset.
• Reset draft state in a batch panel that reverts pending filter controls without changing applied results.
• No-results recovery state with scoped loosen-filter and clear-search actions.
• Saved filter or saved search state showing whether the saved object owns query text.
• Pagination and sort preservation state after filter reset.
• Mobile drawer reset state where returning to results keeps the submitted query.
• Bad state showing query wiped, sort reset, saved identity lost, history deleted, and one-chip removal over-clearing state.

Interaction Contract

• Every reset control names the state it changes.
• Clear filters removes only filter criteria and updates the result count without clearing the search query.
• Clear search removes only query text and leaves filters visible unless the action explicitly says it clears both.
• Removing one chip removes one criterion; Clear all filters removes the filter group only.
• Sort order, view density, search scope, selected saved search, and pagination policy are preserved or explicitly listed as affected.
• No-results recovery keeps active state visible while users choose which constraint to loosen.
• Batch filter reset distinguishes draft selections from applied filters.
• Focus remains near the changed control or result summary after scoped reset.
• Undo or confirmation is available when a broad reset would be surprising or hard to reconstruct.

Implementation Checklist

• Model query, filters, sort, scope, saved identity, pagination, and view mode as separate state owners.
• Name reset functions after the state they affect, such as clearFilters, clearQuery, clearSort, or resetAllResultState.
• Render query tokens separately from filter chips.
• Place Clear filters near applied filter chips and Clear search near the search field or query token.
• Keep one-chip removal, clear-all-filters, reset-draft, clear-query, and reset-all code paths separate.
• Preserve URL parameters and history entries for unrelated state when clearing filters.
• Add no-results recovery actions that loosen filters without erasing query text.
• Test saved filter application and saved search reruns to confirm only the intended state bundle changes.
• Test keyboard focus, mobile filter drawer reset, browser back, pagination, sort, and reload after every reset path.

Common Generated-UI Mistakes

• Implementing Clear filters by reinitializing the whole search page state object.
• Using one Reset button for draft filters, applied filters, query, sort, and saved search.
• Treating query text as just another filter chip without showing the difference.
• Clearing search history or saved search identity when only visible filters were reset.
• Resetting sort and pagination without explaining that the result set was re-ranked or repaged.
• Using Start over in no-results recovery when a scoped Remove date filter action would preserve useful context.
• Applying saved filters as if they were saved searches, clearing query and sort accidentally.

Critique Questions

• What state does this reset control actually own?
• If the label says Clear filters, does the search query survive?
• Can users see query, filters, sort, scope, saved identity, and page state as separate tokens or controls?
• Does one-chip removal affect only one criterion?
• Does no-results recovery preserve the query that produced the empty set?
• What happens to saved search identity, search history, sort, pagination, URL parameters, and focus after reset?