Partial character commit when moving focus to another textbox during IME composition
OS: Windows 10/11 · Device: Desktop or Laptop Any · Browser: Chrome 120+ · Keyboard: Korean (IME) - Microsoft IME
Open case →Scenario
Partial character commit when moving focus to another textbox during IME composition
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-0229-korean-ime-focus-blur-chrome | Windows 10/11 | Desktop or Laptop Any | Chrome 120+ | Korean (IME) - Microsoft IME | draft |
| ce-0230-korean-ime-focus-blur-firefox | Windows 10/11 | Desktop or Laptop Any | Firefox 120+ | Korean (IME) - Microsoft IME | draft |
| ce-0231-korean-ime-focus-blur-safari | macOS 13+ | Desktop (Mac) Any | Safari 17+ | Korean (IME) - macOS Korean Input Method | 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 |
|---|---|---|
| Chrome | — | |
| Firefox | — | |
| Safari | — |
Open a case to see the detailed description and its dedicated playground.
OS: Windows 10/11 · Device: Desktop or Laptop Any · Browser: Chrome 120+ · Keyboard: Korean (IME) - Microsoft IME
Open case →OS: Windows 10/11 · Device: Desktop or Laptop Any · Browser: Firefox 120+ · Keyboard: Korean (IME) - Microsoft IME
Open case →OS: macOS 13+ · Device: Desktop (Mac) Any · Browser: Safari 17+ · Keyboard: Korean (IME) - macOS Korean Input Method
Open case →Other scenarios that share similar tags or category.
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.
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.
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.
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.
Have questions, suggestions, or want to share your experience? Join the discussion below.