v151 · HTML · authoring
Content Authoring Tool
Two live editors side by side — left has autocorrect="on" for prose writing, right has autocorrect="off" for precision fields. Type in both, then sync the text to the other pane and see the difference. Switch the right pane between "prose", "code editor", and "username" scenarios.
Checking autocorrect attribute support…
Right pane scenario:
Undo and autocorrect event probe
The log records real
beforeinput/input events. OS autocorrection may appear as insertReplacementText; undo appears as historyUndo when the browser exposes it.| Editor | Last event | inputType | Text length |
|---|
Live attribute state
| Property | Left editor | Right editor |
|---|
Why this matters for content platforms
- CMS/blog editors — use
autocorrect="on"in the body editor for prose,offfor slug/URL fields, tag inputs, and SEO keyword fields. - Code editors — always
autocorrect="off". Autocorrect corrupts variable names, string literals, and operator sequences. - Translation tools — source language fields use
off(preserve exact source), target fields can useonfor prose orofffor technical content. - Chat / messaging — body of message can be
on, but @mention fields, hashtags, and command inputs should beoff.
see also
implementation reference
Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗