-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
keyboard input in Internet Explorer 10 #352
Comments
When using tests/input.html this is what I get when pressing the letter a: Internet Explorer 10: (* I added spaces before the br-tag to avoid creating line-breaks in this post) Chrome: |
Reproduced, and I think I've got a fix. I'll need to test it a bit first though, to ensure it doesn't break anything else. I'm not sure why this didn't occur when I initially tested the keyboard handling code, but now it seems like IE10 only sets the |
I pushed a fix to https://github.com/Medical-Insight/noVNC/tree/fix-ie10-keyboard If anyone else has time to give it a test run and see if there are any regressions, that'd be really helpful! |
A quick test against IE10 on Windows 7 seems to work well! No problems encountered on Fedora 18 with Firefox 28 and Chrome 34 either, except for the dead keys in Firefox ( #350 ). |
Thanks jalfd! Consistent behavior across all browsers now, most keys working as intended (some keys just aren't recognized under OSX, like ^´`). Browsers tested so far: |
I have now tested with mobile devices that use the normal keyboard code as well: Firefox 28 on Android 4.3 and Safari 7 on iOS 7, it works great! |
…sight/noVNC/tree/fix-ie10-keyboard). Fix keyboard handling for IE10 (issue #352) * Keyboard events in IE10 do not provide any useful information on the properties 'which', 'char' or 'charCode'. Instead, it seems to store the char code in the keyCode property.
When trying to type for example "hello" in noVNC in IE 10 i instead get "85,,/". It is impossible to input normal characters, the only keys that seem to generate the correct input are 1,2,3,4,5,6,7,8,9,0 and the num-pad numbers.
This problem is not present in IE 11, Firefox and Chrome.
Tested on Windows 7.
The text was updated successfully, but these errors were encountered: