Scenario

Number keys for IME candidate selection (Japanese and Chinese)

Many IMEs let users pick candidates with number keys 1–9. In contenteditable, those keys may be consumed by the IME, intercepted by the page for shortcuts, or mis-handled by Safari—causing wrong selection or cancelled composition.

ime
Scenario ID
scenario-ime-composition-number-input

Details

Many IMEs let users pick candidates with number keys 1–9. In contenteditable, those keys may be consumed by the IME, intercepted by the page for shortcuts, or mis-handled by Safari—causing wrong selection or cancelled composition.

Problem Overview

Editor shortcuts (lists, headings) often bind Mod+1 etc.; plain digit keys during IME must reach the IME first.

Observed Behavior

  • Japanese: number selects kanji candidate in Chrome; Safari may differ.
  • Chinese: Pinyin candidate selection with digits on Safari vs Chrome.

Impact

Wrong character committed; composition cancelled if the editor handles keydown too aggressively.

References

Scenario flow

Visual view of how this scenario connects to its concrete cases and environments. Nodes can be dragged and clicked.

React Flow mini map

Variants

Each row is a concrete case for this scenario, with a dedicated document and playground.

Case OS Device Browser Keyboard Status
ce-0191-japanese-ime-number-candidate-selection-chrome Windows 11 Desktop or Laptop Any Chrome 120.0 Japanese (IME) draft
ce-0192-chinese-ime-number-candidate-selection-safari macOS 14.0 Desktop or Laptop Any Safari 17.0 Chinese (IME - Pinyin) draft

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.

Confirmed
Draft
No case documented

Cases

This scenario affects multiple languages. Cases are grouped by language/input method below.

Chinese

1 case

Japanese

1 case

Related Scenarios

Other scenarios that share similar tags or category.

Tags: ime, japanese, chinese, candidate, safari, chrome

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, japanese, chinese, safari, chrome

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
Tags: ime, safari, chrome

IME composition when focus moves between elements (Korean and others)

If the user switches focus to another field, button, or nested contenteditable while Korean (or other) IME composition is active, browsers differ on whether composition is committed, cancelled, or leaves orphan state. Chrome, Safari, and Firefox do not agree; mobile adds more variance.

3 cases
Tags: ime, japanese, chinese

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, chinese, safari

Tab key during IME composition (focus vs indent vs IME)

Tab moves focus by default. During IME composition, Tab may cancel composition, cycle candidates, or be captured by the editor for indentation—behavior differs for Chinese, Thai, and Safari vs Firefox.

2 cases

Comments & Discussion

Have questions, suggestions, or want to share your experience? Join the discussion below.