This project is archived and is in readonly mode.
chrome key recognition of ctrl+enter wrong
Reported by diefans | January 16th, 2011 @ 01:52 PM | in 1.4.0 (closed)
system: ubuntu/lucid 64bit
chrome: 8.0.552.237
mootools: version: '1.3', build:
'a3eed692dd85050d80168ec2c708efe901bb7db3', nocompat
on ctrl+enter chrome is throwing a key code of 10 which is not defined in the Event.Keys object
what about turning around keys and values of Event.Keys to cope with this situation, this would enable mapping more than one code to one key
Comments and changes to this ticket
-
Christoph Pojer February 2nd, 2011 @ 08:21 PM
yes we will change that in future versions to speed up lookups etc.
One question: is this a chrome bug or is this the specification?
-
Christoph Pojer February 23rd, 2011 @ 01:23 PM
- State changed from “new” to “open”
- Milestone set to “1.4.0”
- Milestone order changed from “868” to “0”
-
Christoph Pojer August 13th, 2011 @ 12:53 AM
- Assigned user set to “Arian”
-
Arian August 13th, 2011 @ 01:39 AM
- State changed from “open” to “resolved”
Seems to work fine for me in Chrome on Ubuntu http://jsfiddle.net/arian/K5crE/1/
-
diefans August 13th, 2011 @ 01:49 PM
...mhhhh even though, there is still strange/different behaviour: http://jsfiddle.net/K5crE/2/
in Ubuntu/Firefox I get true for event.control when "ctrl" pressed alone and together with "enter"
Ubuntu/Chrome shows false for a single "ctrl" but true when pressed together with "enter" -
Arian August 13th, 2011 @ 02:16 PM
Seems to be a Chromium issue: http://code.google.com/p/chromium/issues/detail?id=74044. It's set as wontfix with the reason that it's consistent with gecko, but as far as I can see you're right that it's not. I guess you should try to convince them.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Arian
Christoph Pojer
diefans