This feature is non-standard and is not on a standards track. Do not use it on production sites facing the Web: it will not work for every user. There may also be large incompatibilities between implementations and the behavior may change in the future.
This feature has been removed from the Web standards. Though some browsers may still support it, it is in the process of being dropped. Avoid using it and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.
For constants equivalent to these numeric codes, see
Do not use this property anymore, it is deprecated
var value = event.charCode;
valueis the Unicode value of the character key that was pressed.
keypress event, the Unicode value of the key pressed is stored in either the
charCode property, never both. If the key pressed generates a character (e.g. 'a'),
charCode is set to the code of that character, respecting the letter case. (i.e.
charCode takes into account whether the shift key is held down). Otherwise, the code of the pressed key is stored in
When one or more modifier keys are pressed, there are some complex rules for
charCode, see Gecko Keypress Event for the detail.
To get the code of the key regardless of whether it was stored in
charCode, query the
Characters entered through an IME do not register through
charCode. Actually with the Chinese IME I'm using, entering the IME results in a keypress event with keyCode = 229 and no other key events fire until the IME exits (which may happen after multiple characters are inputted). I'm not sure if other IME's work this way.
For a list of the
charCode values associated with particular keys, run the example in Gecko DOM Reference:Examples #Example 7: Displaying Event Object Constants and view the resulting HTML table.
|Document Object Model (DOM) Level 3 Events Specification
The definition of 'KeyboardEvent.charCode' in that specification.
|Obsolete||Initial definition; specified as deprecated|
We're converting our compatibility data into a machine-readable JSON format. This compatibility table still uses the old format, because we haven't yet converted the data it contains. Find out how you can help!
|Feature||Chrome||Edge||Firefox (Gecko)||Internet Explorer||Opera||Safari|
|Basic support||26 (probably earlier)||(Yes)||3||9||12.1||5.1 (probably earlier)|
|Feature||Android||Chrome for Android||Edge||Firefox Mobile (Gecko)||IE Mobile||Opera Mobile||Safari Mobile|
|Basic support||?||?||(Yes)||?||?||?||5.1 (probably earlier)|