KeyboardEvent: code values

The following tables show what code values are used for each native scancode or virtual keycode on major platforms. The reason is that some browsers choose to interpret physical keys differently, there are some differences in which keys map to which codes. These tables show those variations when known.

Code values on Windows

This table shows the Windows scan codes representing keys and the KeyboardEvent.code values which correspond to those hardware keys. Only keys which generate scan codes on Windows are listed.

In the cells, "(❌ Missing)" means that this code value cannot be detected on this browser; "(⚠️ Not the same on xyz)" means that this string represents a different code value on the browser xyz and that special care has to be done when using it.

Code values on Mac

On Mac OS X, it's hard to get scancode or something which can distinguish a physical key from a key event. Therefore, Gecko always maps code value from the virtual keycode.

In the cells,

• "(❌ Missing)" means that this code value cannot be detected on this browser;
• "(⚠️ Not the same on xyz)" means that this string represents a different code value on the browser xyz and that special care has to be done when using it;
• "(⚠️ Same string for 0xab)" means that you cannot distinguished this key with the one matching 0xab;
• "(⚠️ No events fired actually)" means that even if technically you have a specific string for this code, no event will be dispatched;
• "(⚠️ Different string on xyz)" means that the same key will have a different name on browser xyz.

Code values on Linux (X11)

Note that X has too many keys and some of them are not testable with usual keyboard. So, following table is created from source code which maps from scancode to code value.

In the cells, "(❌ Missing)" means that this code value cannot be detected on this browser.

Code values on Firefox for Android