-
Notifications
You must be signed in to change notification settings - Fork 3.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
Quill 1.1.8+ does not react to input properly #1253
Comments
I can't reproduce. Works fine for me. |
No, I can't reproduce it in the codepen either, happens in my application though - I'll try to provide a test case, I'm not sure what's causing it yet. Something must be different between versions since 1.1.7 works fine for me. |
I'm getting some kind of this issue too but with backspace/delete. An actual behavior is same - editor is focused (caret blinks) but no response on character keys until user clicks editor body. Its reproducible for me on playground in Firefox on Windows and OSX:
|
Yup, I can replicate this too, what I'm seeing in my application looks the same, except happens also on enter. |
Do you have any custom key bindings? |
Not that I recall. |
This looks like a duplicate of #1254. Following @cutteroid 's instructions on the most recent 1.2.0 does not exhibit this bug. |
Confirmed, looks like 1.2.0 fixes this. Thank you for all the great work. |
Hello,
I've upgraded qulljs from 1.1.7 to 1.1.9 and input handling seems to be somewhat broken.
Steps for Reproduction
Expected behavior: Some more letters added to the document
Actual behavior: Nothing is printed, delta is not updated. It "looks" like lost focus, because after clicking the editor one can type again until enter is pressed again. However, it is important to note that arrow keys can control caret just fine and enter keypress inserts newline - user just can't type the text. The problem only occurs on firefox, chromium behavior is correct.
Platforms: Linux Ubuntu 16.04, Firefox 50.1.0
Version: versions 1.1.8+ are affected
Version 1.1.7 works fine on both browsers I tested.
The text was updated successfully, but these errors were encountered: