Virtual keyboard on mobile scrolls contenteditable out of view
OS: iOS 17.0 · Device: Mobile iPhone · Browser: Safari 17.0 · Keyboard: System virtual keyboard
Open case →Scenario
Mobile browsers may scroll the page to bring the focused field into view when the virtual keyboard opens—sometimes overscrolling or hiding fixed UI and the caret.
Mobile browsers may scroll the page to bring the focused field into view when the virtual keyboard opens—sometimes overscrolling or hiding fixed UI and the caret.
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-0009-mobile-keyboard-scrolls-page | iOS 17.0 | Mobile iPhone | Safari 17.0 | System virtual keyboard | draft |
Open a case to see the detailed description and its dedicated playground.
OS: iOS 17.0 · Device: Mobile iPhone · Browser: Safari 17.0 · Keyboard: System virtual keyboard
Open case →Other scenarios that share similar tags or category.
On some mobile browsers, focusing a contenteditable programmatically or from a non-gesture path may not raise the virtual keyboard—users cannot type until they tap again.
After the user or the page scrolls while editing in iOS Safari, the caret may render in the wrong place, disappear until the next tap, or sit outside the visible viewport—especially with fixed headers or virtual keyboard resize.
The visual viewport shrinks when the keyboard appears; fixed toolbars, sticky UI, and caret visibility interact with resize and scroll events differently than desktop.
Managing browser UI collisions, virtual keyboard resizing, and IME candidate window positioning.
Automatic scroll-to-caret may fail when the editable is inside nested scrollers, overflow hidden ancestors, or during rapid input—the user loses sight of the insertion point without manual scroll.
Have questions, suggestions, or want to share your experience? Join the discussion below.