-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Bug]: MultiSelect selection results in an infinite loop #16469
Comments
Hello, I just wanted to share some background on this issue since I have been working on it, in case it helps the person that works on it. There was a bug where selecting an item triggered a console warning, which #15818 solved (the warning no longer appeared). However, this caused the UI not to update when updating the items via the However, now programmatic tasks work fine, but when the user takes action it creates an infinite update loop. which is what the issue is referring to. My guess on why the infinite update cycle happens is because we are storing the selected items in two places when the Multiselect is controlled (outside the component and in the Hope this helps |
@tay1orjones We have exact same problem. Any update on ETA ? |
I also have this problem. Considering the severity of this, I hope it can be fixed soon. I subscribed to notifications on this issue. |
+1 on the fix, MultiSelect is unusable, we had to downgrade to 11.56.0. |
completed in #16793 |
Package
@carbon/react
Browser
Chrome
Package version
11.57.0
React version
18
Description
When selecting the first option twice, the multiselect is rerendered in an infinite loop.
Reproduction/example
https://stackblitz.com/edit/github-pxnmha?file=src%2FApp.jsx
Steps to reproduce
Select the first option. Select it again. Select it again. Eventually you'll hit
Suggested Severity
Severity 2 = User cannot complete task, and/or no workaround within the user experience of a given component.
Application/PAL
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: