lang attribute does not affect spellcheck language
OS: macOS Ubuntu 22.04 · Device: Desktop or Laptop Any · Browser: Safari 120.0 · Keyboard: US
Open case →Scenario
lang attribute does not affect spellcheck language
The `lang` attribute on a contenteditable region does not affect the spellcheck language in Safari. Spellcheck always uses the browser's default language, regardless of the `lang` attribute value.
other
Scenario ID
scenario-language-attribute
Details
The lang attribute on a contenteditable region does not affect the spellcheck language in Safari. Spellcheck always uses the browser’s default language, regardless of the lang attribute value.
References
- MDN: spellcheck global attribute - spellcheck documentation
- Stack Overflow: Configure dictionary language spellcheck - Safari limitations
- WHATWG HTML: spellcheck attribute - spellcheck specification
- Macworld: Adjust spell check language in macOS - System settings
- Stack Overflow: Setting spellcheck language in Chrome - Dictionary installation
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-0061-contenteditable-with-lang | macOS Ubuntu 22.04 | Desktop or Laptop Any | Safari 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: spellcheck
Accessibility Foundations: Screen Readers, ARIA, and the AX-Tree
Ensuring contenteditable editors are navigable for assistive technology users through proper ARIA mapping and engine synchronization.
5 cases
Tags: safari
Auto-scroll while typing in contenteditable
Browsers try to keep the caret visible by scrolling the editable container or the page. During rapid typing—especially near the bottom or right edge—scroll updates can lag, batch, or feel jarring, so the caret temporarily leaves the viewport or the view jumps unexpectedly.
3 cases
Tags: safari
beforeinput event is not supported in Safari
The beforeinput event, which is crucial for intercepting and modifying input before it's committed to the DOM, is not supported in Safari. This makes it difficult to implement custom input handling that works across all browsers.
1 case
Tags: safari
innerHTML and serialization differ across browsers
The same DOM edited in contenteditable may serialize to different markup strings in Safari vs Chrome—attribute order, implied tags, and span wrappers for styles.
1 case
Tags: safari
Text caret is invisible on position:relative elements
When editing content inside an element with `position:relative`, the text caret (cursor) is completely invisible. Text can be typed and appears in the editor, but there's no visual feedback of where the insertion point is located.
2 cases
Comments & Discussion
Have questions, suggestions, or want to share your experience? Join the discussion below.