[joy-ui][Select] Bug: Options visually selected after clicking the clear selections button in the Select component
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, react
- Domain
- frontend
Research direction
Start with the Joy UI Select Clear Action example at the linked documentation page and reproduce the stale visual selection after clearing values. Trace the Select component's option-rendering and selection state, then verify that reopening the options menu shows no prior selections after clearing.
Written by the indexing model from the issue text.
Description
Related page
https://mui.com/joy-ui/react-select/
Kind of issue
Broken demo
Issue description
There is a bug in JoyUI's Select component at Clear Action example. When I use the clear selections button, the selected values are removed as expected. However, when I open the options menu again, the previously chosen options still visually appear as selected.
Steps to reproduce:
1- Go to the Select component example page with the clear selections button.
2- Select some options in Select.
3- Click the button to clear selections.
4- Open the Select Options menu again.
Expected behavior:
Options that were previously selected should not visually appear as selected after clicking the clear selections button.
Current behavior:
Options that were previously selected still appear visually as selected after clicking the clear selections button, even though they are no longer selected.
Context
While implementing a Select all option, I realized the effect was not being applied correctly after selecting all the options.
Search keywords: UI, visual bug, clear selection
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Contributor 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 mui/material-ui
-
type: new feature waiting for 👍
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mui/material-ui#48254 · 3 comments · 1 reaction ·
-
has workaround scope: avatar waiting for 👍
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
mui/material-ui#48190 · 5 comments ·
-
has workaround scope: typography type: new feature waiting for 👍
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
mui/material-ui#46488 · 2 comments · 1 reaction ·
-
has workaround scope: text field type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mui/material-ui#37216 · 6 comments ·
-
docs scope: autocomplete
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
mui/material-ui#35713 · 5 comments ·
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100