-
Notifications
You must be signed in to change notification settings - Fork 723
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
Android (chrome): prev keypress is entered #379
Comments
Just confirmed that it also occurs in Firefox for Android! |
Hi @Timmmy! Hmm, to me it appears that the touch event is only showing the last key entered. So the first touch isn't entering anything. For now, try setting the I'll try to spend more time investigating this issue when I get some free time today. |
Hi @Mottie, Thanks for the quick reply. However I found this: When setting an alert after this line, it is clear that the one but last value goes into last.key. This also clarifies that the function is only called once, even with both bindings enabled. Hope this gives you at least a clue? Thanks in advance! |
Hmm, that is very odd.
|
Hi Mottie! You're genious! However I also don't see why this interfers on Android devices. Thanks!! |
I'm glad that fixed the issue! I don't know why the mousewheel would interfere either... I'll take a look at the mousewheel plugin when I get some time. |
I believe I found and fixed the issue causing the previous key to be entered. So no more need to be extra vigilant and ensure the mousewheel plugin isn't being loaded. |
Thanks a lot for the fix! |
Hi!
I've noticed an issue in chrome on Android.
The keyboard inserts the previous stroke instead of current. Except for the first, that one is ok.
For example pressing abcd turns into aabc.
Any ideas?
Occurs on two different devices. Examples on the site van be used to reproduce.
Any ideas?
Thanks in advance!!
Tim
The text was updated successfully, but these errors were encountered: