Chinese IME composition cancelled by scrolling on Android Chrome
OS: Android 14.0 · Device: Phone or Tablet Any · Browser: Chrome 120.0
Open case →Scenario
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.
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.
IME UI is anchored to the caret; scroll changes the viewport without necessarily firing the same events as keyboard-driven caret moves.
Composition cancelled mid-syllable; frustrating on long pages or nested scrollers.
isComposing when possible.Visual view of how this scenario connects to its concrete cases and environments. Nodes can be dragged and clicked.
Each row is a concrete case for this scenario, with a dedicated document and playground.
| Case | OS | Device | Browser | Keyboard | Status |
|---|---|---|---|---|---|
| ce-0194-japanese-ime-scroll-cancels-ios-safari | iOS 17.0 | iPhone or iPad Any | Safari 17.0 | Japanese (IME) | draft |
| ce-0205-chinese-ime-scroll-cancels-android-chrome | Android 14.0 | Phone or Tablet Any | Chrome 120.0 | Chinese (IME - Pinyin) | draft |
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 | — |
This scenario affects multiple languages. Cases are grouped by language/input method below.
OS: Android 14.0 · Device: Phone or Tablet Any · Browser: Chrome 120.0
Open case →OS: iOS 17.0 · Device: iPhone or iPad Any · Browser: Safari 17.0
Open case →Other scenarios that share similar tags or category.
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.
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.
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.
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.
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.
Have questions, suggestions, or want to share your experience? Join the discussion below.