-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[material-ui][Autocomplete] can't be closed with arrow icon #44053
Comments
Thanks for the report @foxylion! This is a regression, we'll be working on it 👍🏼 I can confirm v5 and v6 behavior is different: |
@DiegoAndai Sorry to ping, but why a fast response here while my regression on Autocomplete gets no attention? Please if you don't mind at least checking or ask someone to check... Thanks in advance, |
#43982 might be the solution for this one as well. Working on it. |
#43982 has been merged, and this should be fixed with it. The fix will be included in next week's release. @foxylion, if you have any issues next week, please reach out to @aarongarciah. I'll be out for a couple of weeks, so if you tag me, I won't be able to respond. |
This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue. Note @foxylion How did we do? Your experience with our support team matters to us. If you have a moment, please share your thoughts in this short Support Satisfaction survey. |
Steps to reproduce
Link to live example: https://codesandbox.io/p/sandbox/musing-germain-65rjjp
The issue can also be reproduced in the official docs: https://mui.com/material-ui/react-autocomplete/
Steps:
=> 🔴 does open again automatically on releasing the mouse button
Current behavior
Starting with
@mui/material
version 6 the popover does open again automatically on releasing the mouse buttonExpected behavior
popover should stay closed
Screen recording
Screencast.from.2024-10-09.13-41-48.webm
Your environment
standard CodeSandbox environment
Search keywords: autocomplete close arrow icon
The text was updated successfully, but these errors were encountered: