Docs Editor Model/Schema Cases Scenarios Tips Playground Coverage

Scenario

Space key during composition is ignored or committed inconsistently

Space key during composition is ignored or committed inconsistently

Scenario ID
scenario-space-during-composition
Edit on GitHub

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-0010-space-lost-during-composition Windows 11 Desktop or Laptop Any Edge 120.0 Korean (IME) draft
ce-0183-japanese-ime-space-conversion-chrome Windows 11 Desktop or Laptop Any Chrome 120.0 Japanese (IME) draft
ce-0184-thai-ime-space-ignored-firefox Windows 11 Desktop or Laptop Any Firefox 120.0 Thai (IME) draft
ce-0197-arabic-ime-space-ignored-chrome Windows 11 Desktop or Laptop Any Chrome 120.0 Arabic (IME) draft
ce-0198-hindi-ime-space-ignored-firefox Windows 11 Desktop or Laptop Any Firefox 120.0 Hindi (IME - Devanagari) 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.

Browser Windows
Chrome
ce-0183-japanese-ime-space-conversion-chrome ce-0197-arabic-ime-space-ignored-chrome
120.0, 120.0
Edge
ce-0010-space-lost-during-composition
120.0
Firefox
ce-0184-thai-ime-space-ignored-firefox ce-0198-hindi-ime-space-ignored-firefox
120.0, 120.0
Confirmed
Draft
— No case documented

Cases

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

Arabic

1 case

Hindi/Devanagari

1 case

Japanese

1 case

Korean

1 case

Thai

1 case

Related Scenarios

Other scenarios that share similar tags or category.

Tags: composition, ime

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

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

Browser translation breaks contenteditable editing

When browser translation features (like Google Translate) are activated, they manipulate the DOM by replacing text content and injecting elements. This can break contenteditable functionality, causing cursor positioning issues, event handling problems, and IME composition failures.

1 case
Tags: composition, ime

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.