C-A keydown event have incorrect key property with AZERTY layout
Reported by
mledu...@gmail.com,
Aug 19 2016
|
||
Issue description
UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:48.0) Gecko/20100101 Firefox/48.0
Steps to reproduce the problem:
1. On an AZERTY keyboard, press C-A
2. Inspect the generated keydown event (put a breakpoint in a keydown listener or console.log('%O', event) in a listener or...)
What is the expected behavior?
The key property of the keydown event is 'a'.
What went wrong?
The key property of the keydown event is 'q'.
Did this work before? N/A
Chrome version: <Copy from: 'about:version'> Channel: stable
OS Version:
Flash Version:
The code property is correct: 'KeyQ' (the a key on the AZERTY layout is at the same place as the q on the QWERTY layout).
The keyIdentifier 'U+0041' seems correct
When you only press the a key without Control, the key property is (correctly) 'a'.
,
Aug 23 2016
No acknowledgment?
,
Aug 30 2016
Please someone, tell me that someone actually saw this bug.
,
Sep 8 2016
An example showing the problem: https://jsfiddle.net/mleduque/pp07e1v3/ When I focus the input and hit Ctrl+a, I see "key: q" (french azerty keyboard, linux). Also tested on google chrome 53.
,
Sep 21 2016
Was that the wrong tracker, maybe? I remember that google code should be closed, maybe nobody uses this one anymore?
,
Oct 24 2016
Tested with chrome 54, no changes.
,
Nov 2 2016
Confirming this issue (see [1]). The current behavior of Chrome seems to not conform to the standard, since .key is supposed to reflect the keyboard mapping of the user. Firefox appears to get this right. This is breaking the use of KeyboardEvent.key as a basis for keymaps, and forcing me to stick to the deprecated KeyboardEvent.keyCode. I'd be great if someone could at least acknowledge the issue. [1]: https://github.com/ProseMirror/prosemirror/issues/483
,
Nov 2 2016
This appears to be a duplicate of the similarly quiet https://bugs.chromium.org/p/chromium/issues/detail?id=585241
,
Nov 2 2016
,
Nov 3 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 6 2017
Just checked with chromium 61 on linux on a french keyboard. This seems to have been fixed in the meantime, but that was never notified. So, leaving it closed. |
||
►
Sign in to add a comment |
||
Comment 1 by mledu...@gmail.com
, Aug 22 2016