Samsung Keyboard Link Boundary Node Splitting and Escaping
OS: Android 10-14 · Device: Mobile (Samsung Galaxy series) · Browser: Chrome for Android · Keyboard: Korean (IME) - Samsung Keyboard with Text Prediction ON
Open case →Scenario
Samsung keyboard at link boundaries (node split)
Samsung Keyboard with text prediction can split or duplicate inline link nodes at boundaries—similar to other prediction issues but specific to link-adjacent typing.
ime
Scenario ID
scenario-samsung-keyboard-link-boundary
Details
Samsung Keyboard with text prediction can split or duplicate inline link nodes at boundaries—similar to other prediction issues but specific to link-adjacent typing.
Related Cases
References
Scenario flow
Visual view of how this scenario connects to its concrete cases and environments. Nodes can be dragged and clicked.
Variants
Each row is a concrete case for this scenario, with a dedicated document and playground.
| Case | OS | Device | Browser | Keyboard | Status |
|---|---|---|---|---|---|
| ce-0325-samsung-keyboard-link-boundary-node-split | Android 10-14 | Mobile (Samsung Galaxy series) | Chrome for Android | Korean (IME) - Samsung Keyboard with Text Prediction ON | draft |
Cases
Open a case to see the detailed description and its dedicated playground.
Related Scenarios
Other scenarios that share similar tags or category.
Tags: link
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: android
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
Tags: android
Backspace granularity during Chinese IME on Android
On Android with Chinese IME, Backspace may delete whole syllables, partial Pinyin, or confuse composition boundaries compared to desktop—frameworks that handle Backspace uniformly across platforms mis-handle mobile.
1 case
Tags: android
Duplicate beforeinput or input events during IME composition
Some browsers and keyboards emit duplicate composition-related input or beforeinput events—especially iOS Safari dictation paths and certain Android keyboards—so naive handlers that insert text on every input may double characters or corrupt state.
2 cases
Tags: keyboard
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.
2 cases
Comments & Discussion
Have questions, suggestions, or want to share your experience? Join the discussion below.