Chinese IME composition cancelled by Tab key in Firefox
OS: Windows 11 · Device: Desktop or Laptop Any · Browser: Firefox 120.0
Open case →Scenario
Chinese IME composition cancelled by Tab key in Firefox
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-0189-chinese-ime-tab-cancels-firefox | Windows 11 | Desktop or Laptop Any | Firefox 120.0 | Chinese (IME - Pinyin) | draft |
| ce-0202-thai-ime-tab-cancels-safari | macOS 14.0 | Desktop or Laptop Any | Safari 17.0 | Thai (IME) | 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 | Windows | macOS |
|---|---|---|
| Firefox | — | |
| Safari | — |
This scenario affects multiple languages. Cases are grouped by language/input method below.
OS: Windows 11 · Device: Desktop or Laptop Any · Browser: Firefox 120.0
Open case →OS: macOS 14.0 · Device: Desktop or Laptop Any · Browser: Safari 17.0
Open case →Other scenarios that share similar tags or category.
On Firefox with Windows 10 and Korean IME, specific key combination during IME composition causes the editor to crash. The crash occurs when typing certain sequences with the Korean IME.
Comprehensive system for managing IME (Input Method Editor) composition state across different browsers and IME implementations, including state tracking, event normalization, and cross-platform consistency.
When using IME to input CJK text in heading elements (H1, H2, etc.) in WebKit browsers, pressing Space to confirm composition causes both the raw Pinyin buffer AND the confirmed characters to appear together.
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.
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.
Have questions, suggestions, or want to share your experience? Join the discussion below.