We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Platform: Android 4.2.2; Build/JDQ39; Nexus 7 Browser: Chrome 27.0.1453.90 Used adb logcat for debugging via USB.
I ran tests/input.html and noticed that instead of sending the key event (like it does on the iPad for example) the log shows this message:
I/chromium( 8658): [INFO:CONSOLE(110)] "Key event (keyCode = 229) not found on keyDownList", source: http://:6080/include/util.js(110)
The following keys work as intended: 1,2,3,4,5,6,7,8,9,0,BACKSPACE,ENTER
Running other tests shows that the problem might not be in noVNC but rather in Chrome on Android. I found this issue for the chromium projects that confirm this: http://code.google.com/p/chromium/issues/detail?id=118639
The text was updated successfully, but these errors were encountered:
Fixed by samhed@968431d
Sorry, something went wrong.
No branches or pull requests
Platform: Android 4.2.2; Build/JDQ39; Nexus 7
Browser: Chrome 27.0.1453.90
Used adb logcat for debugging via USB.
I ran tests/input.html and noticed that instead of sending the key event (like it does on the iPad for example) the log shows this message:
I/chromium( 8658): [INFO:CONSOLE(110)] "Key event (keyCode = 229) not found on keyDownList", source: http://:6080/include/util.js(110)
The following keys work as intended: 1,2,3,4,5,6,7,8,9,0,BACKSPACE,ENTER
Running other tests shows that the problem might not be in noVNC but rather in Chrome on Android. I found this issue for the chromium projects that confirm this:
http://code.google.com/p/chromium/issues/detail?id=118639
The text was updated successfully, but these errors were encountered: