If the system is Windows and the native keycode of the pressed key indicates that the key is a-z or 0-9, use a keycode for it.If the inputting character can be inputted with the US keyboard layout, they use the ke圜ode value on the US keyboard layout.įirefox gets ke圜ode values from ASCII characters inputtable by the key - even with shift modifiers or an ASCII capable keyboard layout. Google Chrome, Chromium and Safari must decide the value from the input character. IE just exposes the native virtual keycode value as KeyboardEvent.ke圜ode. The value of key events which are caused by pressing or releasing printable keys in standard position is not compatible between browsers. Unfortunately, some browsers still don't have it, so you'll have to be careful to make sure you use one which is supported on all target browsers.

Instead, you should use de, if it's implemented. You should avoid using this if possible it's been deprecated for some time. If the key can't be identified, this value is 0.

This is usually the decimal ASCII ( RFC 20) or Windows 1252 code corresponding to the key. The deprecated KeyboardEvent.ke圜ode read-only property represents a system and implementation dependent numerical code identifying the unmodified value of the pressed key. Be aware that this feature may cease to work at any time. Avoid using it, and update existing code if possible see the compatibility table at the bottom of this page to guide your decision. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes.

Deprecated: This feature is no longer recommended.

Key code javascript