-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Dropdown: allowAdditions
with Space key does not work
#3994
Comments
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you've completed all the fields in the issue template so we can best help. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can. |
allowAdditions
with Space key does not work
Looks like a valid bug. Also linking #3146 as it can be the same issue. |
@tomasz-grzesik can please you try it on CodeSandbox (https://codesandbox.io/s/jwlr7?module=/example.js)? I can't repro it, only in our docs... |
Unfortunately I can't reproduce it in sandbox. |
@tomasz-grzesik so it's not a regression actually. I don't know from what version we have this behavior however it's related to key handling. This is possible when you have two or more The attached GIFs shows to issues:
I updated https://codesandbox.io/s/zen-sun-q1s0f?file=/example.js to simplify testing and highlight the issue. #4004 will fix it. |
Maby this fix will solve my problem. I will wait for new version and inform you about results. |
Hi, I still have the same problem - can't write the space char inside a new tag.
It can be the problem reason, because when I press space key I see in the modal background another Dropdown is focused and open/close alternately. When I close a Modal I still see Dropdown opened, so the problem is not closed Dropdown after item selection.
|
@tomasz-grzesik Please create a minimal repro on CodeSandbox 🙏 |
Hi,
Why does not the dropdown component allow for space character from version 0.88.0?
It works nice in version 0.87.3.
The text was updated successfully, but these errors were encountered: