feat(suggestion-menu): add a noResults option

[kianbazza]

Summary

Adds noResults to SuggestionMenu.Root.

• 'empty' (the default): the menu stays open and shows Empty, and Enter reaches the host.
• 'close': the menu closes once every search for the query has finished empty (reason 'no-results'). It closes before the empty popup is painted.
  • An update() with the same query leaves it closed, for example when only the caret moved.
  • Any other query searches again, including Backspace, typing more, or a longer query after an empty one.
  • A controlled query that renders after the update() still reopens the menu.

SuggestionMenu.useAsyncMenuCoordinator is available for a "searching…" indicator while results refetch.

Evidence

suggestion-menu.no-results.test.tsx (14 tests):

• The close happens with microtasks only, before any timer or frame.
• The menu waits for loaders before deciding.
• A same-query update stays closed.
• An empty query that settled empty doesn't block a longer one.
• Controlled queries reopen whether they render with the update or after it.
• close() and changing the host forget the empty query.

Checked in Chromium with ProseMirror: /qz closes with no-results, and Backspace to /q reopens with "Quote".

Merge Danger

Door: two-way

Blast Radius: SuggestionMenu, plus a new shared 'no-results' reason

Closes UI-564

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
ui-canary	Ready	Preview	Sep 29, 2026 2:31pm UTC

[linear-code]

UI-564