inputmode attribute does not affect virtual keyboard on mobile
OS: iOS Ubuntu 22.04 · Device: Mobile Any · Browser: Safari 120.0 · Keyboard: System virtual keyboard
Open case →Scenario
The `inputmode` attribute, which should control the type of virtual keyboard shown on mobile devices, does not work on contenteditable regions in iOS Safari. The keyboard type cannot be controlled.
The inputmode attribute, which should control the type of virtual keyboard shown on mobile devices, does not work on contenteditable regions in iOS Safari. The keyboard type cannot be controlled.
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-0059-contenteditable-with-inputmode | iOS Ubuntu 22.04 | Mobile Any | Safari 120.0 | System virtual keyboard | draft |
Open a case to see the detailed description and its dedicated playground.
OS: iOS Ubuntu 22.04 · Device: Mobile Any · Browser: Safari 120.0 · Keyboard: System virtual keyboard
Open case →Other scenarios that share similar tags or category.
On mobile devices, the combination of enterkeyhint and inputmode attributes may affect Enter key behavior inconsistently on contenteditable elements. The Enter key may insert line breaks when it should perform an action, or vice versa.
On iPhone/iPad Safari, when entering text or pressing "return" multiple times in a contenteditable element, the software keyboard appears but hides the text being typed. The page doesn't auto-scroll to keep text visible. Works fine on Android and other browsers.
When a contenteditable element has CSS backdrop-filter applied, rendering may be affected. Text may appear blurry, selection may not render correctly, and performance may be degraded, especially on mobile devices.
On iOS, contenteditable elements may become non-selectable or non-editable. Tapping on the element doesn't display the caret, preventing text input.
On iOS Safari, when the software keyboard becomes visible, viewport calculations become unreliable. `position:fixed` elements break, `height` returns incorrect values, and absolute positioning with `top`/`bottom` fails. This severely affects editors with floating toolbars or positioned elements.
Have questions, suggestions, or want to share your experience? Join the discussion below.