input event is fired synchronously when the value of an
<textarea> element is changed. Additionally, it fires on
contenteditable editors when its contents are changed. In this case, the event target is the editing host element. If there are two or more elements which have
contenteditable as true, "editing host" is the nearest ancestor element whose parent isn't editable. Similarly, it's also fired on root element of
- HTML5, DOM Level 3 Events
- Default Action
- The value or the content is modified.
||The event target (the topmost target in the DOM tree).|
||The type of event.|
||Does the event normally bubble?|
||Is it possible to cancel the event?|
|Feature||Chrome||Firefox (Gecko)||Internet Explorer||Opera||Safari|
||(Yes)||12 (12)||(Yes)||Not supported||(Yes)|
Event target is the innermost element at caret position.
||Not supported||31 (31)||Not supported||Not supported||Not supported|
|Feature||Android||Chrome for Android||Firefox Mobile (Gecko)||IE Mobile||Opera Mobile||Safari Mobile|
||Not supported||Not supported||31.0 (31)||Not supported||Not supported||Not supported|
Prior to Gecko 12.0 (Firefox 12.0 / Thunderbird 12.0 / SeaMonkey 2.9), Gecko didn't fire input events while composition was ongoing using IMEs or when dead keys were used on the Mac.
change event is related.
change fires less often than
input – it only fires when the changes are committed by the user.