Chrome v96 performance regression with spell checking in large contenteditable
OS: Any Any · Device: Desktop or Laptop Any · Browser: Chrome 96 · Keyboard: US
Open case →Scenario
Chrome v96 performance regression with spell checking in large contenteditable
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-0324-chrome-v96-performance-regression-spellcheck | Any Any | Desktop or Laptop Any | Chrome 96 | US | draft |
Open a case to see the detailed description and its dedicated playground.
OS: Any Any · Device: Desktop or Laptop Any · Browser: Chrome 96 · Keyboard: US
Open case →Other scenarios that share similar tags or category.
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.
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.
When a ResizeObserver is attached to a contenteditable element, the observer may trigger during editing as content changes size. This can cause layout recalculations and visual jumps, especially when the contenteditable has dynamic height.
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.
Ensuring contenteditable editors are navigable for assistive technology users through proper ARIA mapping and engine synchronization.
Have questions, suggestions, or want to share your experience? Join the discussion below.