v152 · 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:

Prose editor autocorrect=on

Start typing here. Try misspelling words like "recieve" or "teh" to see autocorrect in action.

0 chars

Code editor autocorrect=off

Type code, a username, or a search query. Autocorrect stays silent here.

0 chars

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, off for 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 use on for prose or off for technical content.
Chat / messaging — body of message can be on, but @mention fields, hashtags, and command inputs should be off.

Why this matters for content platforms

see also