Autocomplete disableCloseOnSelect ignored if blurOnSelect
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
Duplicates
- I have searched the existing issues
Latest version
- I have tested the latest version
Current behavior 😯
If Autocomplete has the property disableCloseOnSelect, it does not work if we also set blurOnSelect.
The choice selector closes.
Expected behavior 🤔
The choice selector should remain open. Or the documentation should inform that the two cannot cohabit.
<Autocomplete
{...defaultProps}
id="disable-close-on-select-with-blurOnSelect"
disableCloseOnSelect
blurOnSelect
renderInput={(params) => (
<TextField {...params} label="with blurOnSelect" variant="standard" />
)}
/>
Steps to reproduce 🕹
Link: codesandbox.io/s/playground-demo-material-ui-forked-lbply2?file=/demo.js
Context 🔦
No response
Your environment 🌎
npx @mui/envinfo
Don't forget to mention which browser you used.
Output from `npx @mui/envinfo` goes here.
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.
Research direction
Start with the Autocomplete behavior shown in the linked CodeSandbox, using the example that combines disableCloseOnSelect and blurOnSelect. Reproduce the closing behavior and trace how those two properties interact. Done means either the selector remains open as expected or the documentation clearly explains that the properties cannot be combined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100