Steps to reproduce the problem:
When I investigate KeyboardEvent.key mapping on Android from the source code, some values whose mapping are not suggested by the spec are different from Firefox.

What is the expected behavior?

What went wrong?
virtual keycode	Gecko	Chromium

AKEYCODE_SWITCH_CHARSET (95)	"ModeChange"	"Unidentified"

"ModeChange" is declared as "The Mode Change key, to toggle between or cycle through input modes of IMEs.", and KEYCODE_SWITCH_CHARSET is explained as "Key code constant: Switch Charset modifier key. Used to switch character sets (Kanji, Katakana)". I understood the explanation as "changing keyboard layout", but if the keycode doesn't mean it, Firefox should change it to "Unidentified".

AKEYCODE_FORWARD (125)	"BrowserForward"	"MediaSkip"

KEYCODE_FORWARD is explained as "Key code constant: Forward key". Although, this is very unclear. However, when I connect keyboard to Nexus 7 (2013), BrowserForward key generates this keycode. So, I think that Chromium should use "BrowserForward" same as Firefox.

AKEYCODE_NUMPAD_ENTER (160)	"Enter"	"Unidentified"

Although, I cannot reproduce this odd mapping actually with Google Chrome. Perhaps, DomKey::FromCharacter() or something called in DomKey GetDomKeyFromAndroidEvent() solves this, but looks like that it should be mapped in GetDomKeyFromAndroidKeycode() explicitly.

AKEYCODE_BOOKMARK (174)	"BrowserFavorites"	"Unidentified"

Although, I cannot test this because I don't find keyboard which can generate this keycode actually yet. However, the explanation of this keycode is, "Key code constant: Bookmark key. On some TV remotes, bookmarks content or web pages.". So, this should be mapped to "BrowserFavorites".

AKEYCODE_LANGUAGE_SWITCH (204)	"GroupNext"	"Unidentified"

The explanation is, "Key code constant: Language Switch key. Toggles the current input language such as switching between English and Japanese on a QWERTY keyboard. On some devices, the same function may be performed by pressing Shift+Spacebar." So, I think that this should be mapped to "GroupNext" because ISO_Next_Group keysym on Linux works as so.

AKEYCODE_MUHENKAN (213)	"NonConvert"	"Unidentified"
AKEYCODE_HENKAN (214)	"Convert"	"Unidentified"

These keys are "無変換" and "変換" keys of JIS keyboard and they actually cause these keycodes. So, Chromium should use them.

Did this work before? No 

Does this work in other browsers? N/A

Chrome version:   Channel: n/a
OS Version: 
Flash Version: