Android: First word duplication after space + backspace
OS: Android 14.0 · Device: Smartphone Any · Browser: Chrome 131.0
Open case →Scenario
IME composition triggers deleteContentBackward and insertText events sequentially in iOS Safari
IME composition triggers deleteContentBackward and insertText events sequentially in iOS Safari
Scenario ID
scenario-ime-composition-duplicate-events
Scenario flow
Visual view of how this scenario connects to its concrete cases and environments. Nodes can be dragged and clicked.
Variants
Each row is a concrete case for this scenario, with a dedicated document and playground.
| Case | OS | Device | Browser | Keyboard | Status |
|---|---|---|---|---|---|
| ce-0096-ime-composition-duplicate-events-ios-safari | iOS 17.0 | iPhone or iPad Any | Safari 17.0 | Korean (IME) | draft |
| ce-0577-android-first-word-duplication | Android 14.0 | Smartphone Any | Chrome 131.0 | Gboard (English/Korean) | confirmed |
Browser compatibility
This matrix shows which browser and OS combinations have documented cases for this scenario. Click on a cell to view the specific case.
| Browser | Android | iOS |
|---|---|---|
| Chrome | — | |
| Safari | — |
Confirmed
Draft
— No case documented
Cases
This scenario affects multiple languages. Cases are grouped by language/input method below.
Gboard (English/Korean)
1 caseKorean
1 caseIME composition triggers deleteContentBackward and insertText events sequentially in iOS Safari
OS: iOS 17.0 · Device: iPhone or iPad Any · Browser: Safari 17.0
Open case →Related Scenarios
Other scenarios that share similar tags or category.
Tags: ime, beforeinput, ios, safari, duplicate-events
iOS dictation triggers duplicate input events after completion
On iOS, when using voice dictation to input text into contenteditable elements, the system may fire duplicate beforeinput and input events after the initial dictation completes. The text is split into words and events are re-fired, causing synchronization issues. Composition events do not fire during dictation, making it difficult to distinguish dictation from keyboard input.
1 case
Tags: composition, ime, beforeinput, safari
insertParagraph preventDefault breaks IME composition state in Safari
In Safari desktop, when preventDefault() is called on keydown or beforeinput events for insertParagraph (Enter key), the IME composition state becomes corrupted. Subsequent text input fails to trigger proper input events, causing characters to not be inserted or composition to malfunction.
3 cases
Tags: composition, ime, beforeinput
beforeinput and input events have different inputType values
During IME composition or in certain browser/IME combinations, the beforeinput event may have a different inputType than the corresponding input event. For example, beforeinput may fire with insertCompositionText while input fires with deleteContentBackward. This mismatch can cause handlers to misinterpret the actual DOM change and requires storing beforeinput's targetRanges for use in input event handling.
1 case
Tags: composition, ime, beforeinput
Selection mismatch between beforeinput and input events
The selection (window.getSelection()) in beforeinput events can differ from the selection in corresponding input events. This mismatch can occur during IME composition, text prediction, or when typing adjacent to formatted elements like links. The selection in beforeinput may include adjacent formatted text, while input selection reflects the final cursor position.
1 case
Tags: composition, ime, beforeinput
getTargetRanges() returns empty array in beforeinput events
The getTargetRanges() method in beforeinput events may return an empty array or undefined in various scenarios, including text prediction, certain IME compositions, or specific browser/device combinations. When getTargetRanges() is unavailable, developers must rely on window.getSelection() as a fallback, but this may be less accurate.
1 case
Comments & Discussion
Have questions, suggestions, or want to share your experience? Join the discussion below.