KeyboardEvent.keyCode Deprecated

[Zauberbutter]

Because of the deprecation of keyCode should the KeyboardEvent.code attribute not be supported? See the keyCode search results.

[carmacleod]

Agree we should replace uses of KeyboardEvent.keyCode and KeyboardEvent.which to keep current, particularly now that the latest Edge supports the newer api.

Note that we will need to use KeyboardEvent.key to look for non-printable keys like arrows and escape (not KeyboardEvent.code).

• deprecated KeyboardEvent.keyCode
• deprecated KeyboardEvent.which
• KeyboardEvent.key (example code shows one way to handle non-standard IE values if needed)
• KeyboardEvent.key values

Here are the KeyboardEvent.key values that we will typically need (note that they are strings):

• "ArrowDown"
• "ArrowLeft"
• "ArrowRight"
• "ArrowUp"
• "Home"
• "End"
• "PageUp"
• "PageDown"
• "Enter"
• "Tab"
• "Escape"
• " " (for space key)

We can still use KeyboardEvent.ctrlKey, altKey, shiftKey and metaKey to check for modifiers.

We may want to do something like the following to be sure we work in older browsers?

var key = event.key || event.keyCode;
if (key === 'Escape' || key === 'Esc' || key === this.keyCode.ESC /* 27 */) { ... }

[css-meeting-bot]

The ARIA Authoring Practices (APG) Task Force just discussed keyCode Deprecation.

The full IRC log of that discussion

<carmacleod> TOPIC: keyCode Deprecation
<carmacleod> github: https://github.com//issues/1350
<carmacleod> mck: should we add this to our code guide?
<carmacleod> Jemma: good idea

Also, Jon mentioned that we should not have common "util" methods for these, because we want each example to be self-contained and self-explanatory, so we don't want stuff hiding in util methods. Folks agreed that "no utils" is best.