Arabic IME character joining and RTL direction issues in Safari
OS: macOS 14.0 · Device: Desktop or Laptop Any · Browser: Safari 17.0
Open case →Scenario
Arabic IME character joining and RTL direction issues in Safari
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-0179-arabic-ime-character-joining-safari | macOS 14.0 | Desktop or Laptop Any | Safari 17.0 | Arabic (IME) | draft |
| ce-0207-hebrew-ime-rtl-composition-firefox | Windows 11 | Desktop or Laptop Any | Firefox 120.0 | Hebrew (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: macOS 14.0 · Device: Desktop or Laptop Any · Browser: Safari 17.0
Open case →OS: Windows 11 · Device: Desktop or Laptop Any · Browser: Firefox 120.0
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.
Advanced handling of language-specific input behaviors, BiDi layout, and syllabic granularity.
In Safari desktop, when preventDefault() is called on keydown or beforeinput events for insertParagraph (Enter key), the IME composition state becomes corrupted. Subsequent text input fails to trigger proper input events, causing characters to not be inserted or composition to malfunction.
On macOS, using the accent menu (e.g., holding vowel key to select accented character, or using option+key combinations) does NOT consistently trigger standard IME composition events (`compositionstart`, `compositionupdate`, `compositionend`). This makes it difficult to distinguish accent menu input from IME input or regular keyboard input.
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.
Have questions, suggestions, or want to share your experience? Join the discussion below.