-
Notifications
You must be signed in to change notification settings - Fork 10
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
Chrome problems #4
Comments
Hi. Can you do (function( global ) {
try {
return (new global["KeyboardEvent"]( "keyup", {"key": "a"} ))["key"] == "a";
}
catch ( __e__ ) {
return false;
}
})( this ) in console and comment here the answer. If it true and By the way, your case is working in my chrome currectly: http://clip.corp.mail.ru/clip/m198/1373747235-clip-50kb-xFUheGw5hJBc.png |
Yes, that demo works, as in: The
and it outputs
etc. When entering
etc. So, everything seems to be working on that page. I'll have to check my code more thoroughly. Sorry about the noise. |
That's all right! |
Hi, this doesn't seem to work in Chrome (version 27.0.1453.116, Windows 7).
When entering the demo code into the Javascript console:
... the console starts outputting
... as if the key and char properties are not populated.
Is this perhaps related to https://bugs.webkit.org/show_bug.cgi?id=16735 ?
The text was updated successfully, but these errors were encountered: