Chinese IME backspace deletes entire composition instead of last character
OS: Android 11.0+ · Device: Any Android device Any · Browser: Chrome Mobile 100.0+ · Keyboard: Chinese (Pinyin) IME
Open case →Scenario
Backspace granularity during Chinese IME on Android
On Android with Chinese IME, Backspace may delete whole syllables, partial Pinyin, or confuse composition boundaries compared to desktop—frameworks that handle Backspace uniformly across platforms mis-handle mobile.
ime
Scenario ID
scenario-ime-backspace-chinese-mobile
Details
On Android with Chinese IME, Backspace may delete whole syllables, partial Pinyin, or confuse composition boundaries compared to desktop—frameworks that handle Backspace uniformly across platforms mis-handle mobile.
Related Cases
References
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-0219-chinese-ime-backspace-android | Android 11.0+ | Any Android device Any | Chrome Mobile 100.0+ | Chinese (Pinyin) IME | draft |
Cases
Open a case to see the detailed description and its dedicated playground.
Related Scenarios
Other scenarios that share similar tags or category.
Tags: ime, chinese, android
Scrolling cancels or disrupts IME composition
User scrolling the page or scrollable editor while the IME candidate window is open may cancel composition or move the caret out of sync—reported on iOS Safari with Japanese IME and Android Chrome with Chinese IME when scroll containers move the editing context.
2 cases
Tags: ime, android
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
Tags: ime, chinese
IME candidate list timing and conversion (kanji, hanzi)
Japanese kanji conversion and Chinese character selection depend on the IME candidate window. Delays, wrong ordering, or Safari-specific lag can cause users to commit the wrong character or see candidates that do not match the underlying buffer—especially under load or in complex layouts.
2 cases
Tags: ime, android
Duplicate beforeinput or input events during IME composition
Some browsers and keyboards emit duplicate composition-related input or beforeinput events—especially iOS Safari dictation paths and certain Android keyboards—so naive handlers that insert text on every input may double characters or corrupt state.
2 cases
Tags: ime, chinese
Blur and focus during IME composition (CJK and Japanese Safari)
Moving focus away from the editor while composing text (Chinese, Japanese, Korean) can cancel composition, commit partial text, or leave the IME candidate window out of sync. Safari often shows distinct behavior for Japanese; Chrome behavior for Chinese/Korean is covered in related cases.
2 cases
Comments & Discussion
Have questions, suggestions, or want to share your experience? Join the discussion below.