Created attachment 8645341 [details] Firefox KeyboardEvent bug.png I've tested the new DOM3 KeyboardEvent.code functionality in Firefox 39 on windows 10 with my French keyboard, and compared the values it returned with the W3C specification. What I found is that the value that Firefox returns for the key named 'IntlHash' in the specification (§1.1.4 - Standard "102" Keyboard Layout") is wrong. The code that Firefox returns for that key is 'Backslash'. I attached a screenshot showing what I get using the W3C Keyboard Event test.
Component: General → Event Handling
Product: Firefox → Core
'*' gives backslash on Finnish keyboard too, though this keyboard is far from that 102. I wonder why the spec even has that 102.
Hmm, both Backslash key on 102 keyboard and IntlHash key on French/Finnish cause scancode 0x2B without extended flag. For distinguishing them, we need to know what type of physical keyboard is connected and used...
Uh, Chromium also returns "Backslash" for the key on Win 10...
Oh, I completely forgot writing this comment: http://mxr.mozilla.org/mozilla-central/source/widget/NativeKeyToDOMCodeName.h#144 > 144 // Win: IntlHash's scan code is shared with "Backslash" key. > 145 // Mac: IntlHash's virtual key code is shared with "Backslash" key. > 146 // X11: IntlHash's scan code is shared with "Backslash" key. > 147 // Android: IntlHash's scan code is shared with "Backslash" key. It seems that we should propose to remove "IntlHash" value from the spec?
sounds like so yes.
Assignee: nobody → masayuki
Status: UNCONFIRMED → ASSIGNED
Component: Event Handling → DOM: Events
Ever confirmed: true
OS: Unspecified → All
Hardware: Unspecified → All
Now, "IntlHas" was dropped fro the spec due to impossible mapping.
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.