Closed
Bug 792802
Opened 13 years ago
Closed 13 years ago
keyCode of all key events for Hankaku_Zenkaku key is broken.
Categories
(Core :: DOM: Events, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: taka, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:15.0) Gecko/20100101 Firefox/15.0.1
Build ID: 20120907231835
Steps to reproduce:
I hit the Hankaku_Zenkaku key on a Japanese keyboard.
Actual results:
The keyCode of a key event generated for a Hankaku_Zenkaku key is always zero.
Expected results:
The keyCode for a Hankaku_Zenkaku key should be 243 or 244, which should be selected alternately every time you hit the key.
This should work like:
<Hit the key>
keyup : keyCode=243
keydown : keyCode=244
<Hit the key>
keyup : keyCode=244
keydown : keyCode=243
<Hit the key>
keyup : keyCode=243
keydown : keyCode=244
<Hit the key>
keyup : keyCode=244
keydown : keyCode=243
Comment 1•13 years ago
|
||
Is the problem limited to firefox?
Updated•13 years ago
|
Component: Untriaged → General
Product: Firefox → Core
Comment 2•13 years ago
|
||
We don't want to add more keyCode values newly anymore. If you can see the values with Fx14 or earlier on Windows, they are just same as native keycode values which were passed unexpectedly (I mean that it was bug). On Linux, they must be zero even with Fx14 or earlier. And the key behavior on Window is completely strange. Even we will implement .key, it won't be supported on Windows because the native virtual keycode values are VK_OEM_AUTO and VK_OEM_ENLW, they have no meaning. (I'm still thinking the behavior on Linux though.)
# We don't want to support the keys which are not available on all platforms...
-> INVA
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Component: General → DOM: Events
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•