-
Notifications
You must be signed in to change notification settings - Fork 582
Fix event consuming for textareas #602
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
Conversation
This is useful when this component is used with texareas.
|
Hey @moroshko |
|
Is there a plan to get this (or #522) merged in the near future? I'm currently using a forked version of the library and would like to be able to update to latest. |
|
Hi @RoiEXLab are you still interested in this? I'd be happy to merge it if you've got a minute to rebase it and add a test. If not no worries, but I'll close this PR in a few days. |
|
Hey @pimterry rebasing the PR is easy, just did it. |
|
Ok, no worries @RoiEXLab. I've added a couple of quick tests here, which should give us a little coverage of this. Thanks for the contribution! 👍 |
|
Thanks, when can we expect a new npm release? |
|
Now released as v10.0.4 🎉 |
I'm using this component for multiline TextFields (i.e.
<textarea>Value</textarea>in raw html)And it works, but there is this slight annoyance that every time I press enter to select a suggestion using the keyboard, I add another line to the textarea.
Also when no suggestions are being displayed, I want to be able to freely navigate through the textarea by using arrow keys.
This is the simplest fix i could come up with to prevent that.