Virtual scrolling libraries interfere with contenteditable selection
OS: macOS 14.0 · Device: Desktop or Laptop MacBook Pro · Browser: Chrome 120.0 · Keyboard: US
Open case →Scenario
Virtual scrolling libraries interfere with contenteditable selection
When a contenteditable element is used with virtual scrolling libraries (e.g., for large documents), the virtual scrolling mechanism may interfere with text selection and caret positioning. The selection may be lost when elements are removed from the DOM during scrolling.
performance
Scenario ID
scenario-virtual-scrolling
Details
When a contenteditable element is used with virtual scrolling libraries (e.g., for large documents), the virtual scrolling mechanism may interfere with text selection and caret positioning. The selection may be lost when elements are removed from the DOM during scrolling.
References
- TipTap Issue #2629: iOS Safari selection visible after scroll - iOS Safari selection bugs
- Stack Overflow: Saving and restoring caret position - Caret restoration patterns
- ProseMirror: Documentation - Logical position system
- NPM: use-editable - React hook for caret preservation
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-0078-contenteditable-with-virtual-scrolling | macOS 14.0 | Desktop or Laptop MacBook Pro | Chrome 120.0 | US | 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: performance, chrome, macos
CSS filter may affect contenteditable performance
When a contenteditable element has CSS filters applied (blur, brightness, etc.), editing performance may be degraded. Typing may lag, and selection may be slow to update.
1 case
Tags: performance, chrome, macos
CSS will-change may improve or degrade contenteditable performance
When a contenteditable element has CSS will-change property set, performance may be affected. In some cases, it may improve performance by hinting the browser about upcoming changes. In other cases, it may degrade performance by creating unnecessary layers.
1 case
Tags: performance, chrome
Chrome spellcheck performance regression (v96 era)
A known Chromium regression around spellcheck and large contenteditable regions caused severe typing lag—documented for planning workarounds such as spellcheck=false or chunking.
1 case
Tags: performance, macos
MutationObserver may interfere with contenteditable editing
When a MutationObserver is attached to a contenteditable element or its parent, the observer callbacks may interfere with editing performance. Frequent DOM mutations during typing can trigger many observer callbacks, causing lag or jank.
1 case
Tags: performance, selection
Selection performance in large contenteditable documents
getSelection(), getRangeAt, and DOM walks over very large contenteditable trees can block the main thread when the user selects all or drags across thousands of nodes—mobile devices suffer first.
1 case
Comments & Discussion
Have questions, suggestions, or want to share your experience? Join the discussion below.