compositionupdate event is fired when a character is added to a passage of text being composed (fires with special characters that require a sequence of keys and other inputs such as speech recognition or word suggestion on mobile).
- DOM L3
- Default Action
||Focused element processing the composition, null if not accessible.|
||The type of event.|
||Does the event normally bubble?|
||Is it possible to cancel the event?|
||DOMString (string)||The original string being edited, otherwise the empty string. Read only.|
||DOMString (string)||The language code for the composition event, if available; otherwise, the empty string. Read only.|
|Feature||Chrome||Firefox (Gecko)||Internet Explorer||Opera||Safari|
Not dispatched immediately after
|9.0 (9.0)||(Yes)||Not supported||?|
|Feature||Android||Firefox Mobile (Gecko)||IE Mobile||Opera Mobile||Safari Mobile|
|Basic support||?||9.0 (9.0)||?||?||?|
compositionupdate events are fired before editor contents are actually changed; that is, the value of an editable element has not yet been changed when
compositionupdate event handlers are called. Starting in Gecko 12.0 (Firefox 12.0 / Thunderbird 12.0 / SeaMonkey 2.9),
input events are fired while editing is underway, after the contents of the element are changed. This lets you get the updated contents while editing is underway.
localeattribute for trusted events yet. However, web developers can set this value via
initCompositionEvent()when creating untrusted events.