feat(naked_ui,remix): show and announce a combobox 'no results' state
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- accessibility, frontend
Research direction
Start by reading the NakedComboboxState and RemixCombobox implementations, then inspect the combobox specs and combobox.mdx plus the skill. Trace how completed searches and caret-only changes are distinguished so the empty result is announced once per completed search. Done means the state, optional styled empty slot, live announcement, matching spec slot, and documentation are covered.
Written by the indexing model from the issue text.
Description
Problem
When a query matches nothing, the RemixCombobox suggestion panel closes and nothing tells the user that the search ran and found nothing. This affects visual users, and screen-reader users get no announcement either.
NakedCombobox deliberately avoids announcing an empty result for searches that never ran (disabled, or a discarded query). A completed search with zero results is a different case and deserves feedback.
Seen while reviewing #401 (screenshots 07/17: the query zzzz closes the panel silently).
Proposal
- naked_ui: expose the "completed with no results" state on
NakedComboboxState. It must stay distinct from "no search yet" and "search discarded". - remix: add an optional empty-state slot to
RemixCombobox, for exampleemptyBuilderor a localizable label, plus a matching spec slot so presets can style it. - Semantics: announce the empty result once per completed search, through a live region, without repeating on caret-only changes.
- Docs: cover the new state in
combobox.mdxand the skill.
Out of scope for #400/#401
This is a feature, not a correctness fix, so it is tracked separately rather than added to the open PRs.
- Dominant language
- Dart
- Stars
- 24
- Forks
- 5
- Avg merge
- 15h 29m
- Merged PRs (30d)
- 144
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from btwld/remix
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 Half a day Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 Half a day Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 Half a day Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
AppFlowy-IO/AppFlowy#9147 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
ccch1mneyyy/dsh-Go#1682 ·
Maintainers usually reply within 1 day
-
help wanted
Difficulty 1/5 Under an hour Newbie friendliness 76/100
pesaclarity/ujumbe-parsers#64 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
patarapolw/lingua_srs#278 ·
Maintainers usually reply within 1 day