154207 - Implement DOM 2 VK_ keyboard constants

Status: VERIFIED WONTFIX

(Core :: DOM: UI Events & Focus Handling, defect)

Description

[Aaron Leventhal]

We don't currently support constants such as VK_AT, VK_COLON or all of the other
keyboard consts at:

http://www.w3.org/TR/1999/WD-DOM-Level-2-19990719/events.html#Level2-Events-UIEvent

Not supporting these creates a limitation when authoring chrome keybindings.

Comment 1

[Kyle Yuan]

complete list of missing constants:

VK_ACCEPT
VK_AGAIN
VK_ALL_CANDIDATES
VK_ALPHANUMERIC
VK_ALT_GRAPH
VK_AMPERSAND
VK_ASTERISK
VK_AT
VK_BRACELEFT
VK_BRACERIGHT
VK_CIRCUMFLEX
VK_CODE_INPUT
VK_COLON
VK_COMPOSE
VK_CONVERT
VK_COPY
VK_CUT
VK_DEAD_ABOVEDOT
VK_DEAD_ABOVERING
VK_DEAD_ACUTE
VK_DEAD_BREVE
VK_DEAD_CARON
VK_DEAD_CEDILLA
VK_DEAD_CIRCUMFLEX
VK_DEAD_DIAERESIS
VK_DEAD_DOUBLEACUTE
VK_DEAD_GRAVE
VK_DEAD_IOTA
VK_DEAD_MACRON
VK_DEAD_OGONEK
VK_DEAD_SEMIVOICED_SOUND
VK_DEAD_TILDE
VK_DEAD_VOICED_SOUND
VK_DOLLAR
VK_EURO_SIGN
VK_EXCLAMATION_MARK
VK_FINAL
VK_FIND
VK_FULL_WIDTH
VK_GREATER
VK_HALF_WIDTH
VK_HIRAGANA
VK_INVERTED_EXCLAMATION_MARK
VK_JAPANESE_HIRAGANA
VK_JAPANESE_KATAKANA
VK_JAPANESE_ROMAN
VK_KANA
VK_KANJI
VK_KATAKANA
VK_KP_DOWN
VK_KP_LEFT
VK_KP_RIGHT
VK_KP_UP
VK_LEFT_PARENTHESIS
VK_LESS
VK_MINUS
VK_MODECHANGE
VK_NONCONVERT
VK_NUMBER_SIGN
VK_PASTE
VK_PLUS
VK_PREVIOUS_CANDIDATE
VK_PROPS
VK_QUOTEDBL
VK_RIGHT_PARENTHESIS
VK_ROMAN_CHARACTERS
VK_STOP
VK_UNDEFINED
VK_UNDERSCORE
VK_UNDO

I really need VK_PLUS/VK_MINUS for Numpad +/-

Comment 2

[Aaron Leventhal]

DOM 3 events link:
http://www.w3.org/TR/2002/WD-DOM-Level-3-Events-20020208/idl-definitions.html

It seems to be missing a lot of the constants from level 2.

Comment 3

[Takeshi Kurosawa :takenspc]

+masayuki

I wonder that there's still a plan to extend VK_* constants as UI Events spec says:

https://w3c.github.io/uievents/#ref-for-character-value-1

> This specification does not define values for either keyCode or charCode, or behavior for charCode. In conforming UI Events implementations, content authors can instead use key and code.

Comment 4

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)(sickish, maybe slower respose)]

Basically, I don't want to change .keyCode implementation anymore and at least Blink doesn't define the constants. So, we don't need to define them.

I think that we can close this as INVA or WONTFIX.

Comment 5

[Olli Pettay [:smaug][[e-mail]]]

yeah, since the spec doesn't really define DOM_VKs, I don't think we have anything to do here.
WONTFIX is fine to me. Please reopen if you disagree.

Comment 6

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)(sickish, maybe slower respose)]

Thank you, I agree with closing this bug.