v149 · html · forms · accessibility

Respect autocorrect="off" for Windows touch keyboard in TSF

Chrome 149 makes Chrome on Windows honour autocorrect="off" for the Windows on-screen touch keyboard (via the Text Services Framework), matching the behaviour already present on other platforms and in other browsers.

at a glance

Shipped in	Chrome 149 (Windows desktop, touch keyboard path)
Status	Enabled by default
Flag	None — on by default
Spec	HTML Living Standard §Autocorrection
Standards position (Firefox)	No signal
Standards position (Safari)	No signal
ChromeStatus	5196629995028480 — Respect autocorrect="off" for Windows touch keyboard in TSF

Source: chromestatus.com/feature/5196629995028480

Shipped-versus-proposed disagreement, both sides reported rather than resolved (fetched 2026-10-07): this page says the change shipped in "Chrome 149 (Windows desktop, touch keyboard path)" with status "Enabled by default", while the ChromeStatus feature 5196629995028480 reports status "Proposed" with desktop 149 (record created 2026-02-26, updated 2026-05-04). Neither side is adjudicated here.

why it exists

The HTML autocorrect attribute lets authors tell the browser whether to apply automatic text correction to an editable element. Setting autocorrect="off" is important for fields where verbatim input matters — code editors, username fields, password-visible inputs, search boxes that accept technical terms, and so on.

On Windows, Chrome routes touch-keyboard input through the Text Services Framework (TSF). Before Chrome 149, the autocorrect="off" attribute was not forwarded to TSF, so the touch keyboard would still apply its built-in autocorrections regardless of what the page specified. Chrome 149 closes this gap: TSF is now instructed to suppress autocorrection when the focused element carries autocorrect="off".

Source: chromestatus feature summary; HTML Living Standard §Autocorrection

shape of the API

No new API. The change is a behavioural fix to the existing autocorrect content attribute.

Attribute	Element	Effect in Chrome 149+ (Windows touch)
`autocorrect="on"` (default)	`<input>`, `<textarea>`, `contenteditable`	TSF autocorrection active — same as before
`autocorrect="off"`	`<input>`, `<textarea>`, `contenteditable`	TSF autocorrection suppressed — newly fixed in Chrome 149

Source: HTML Living Standard §Autocorrection

example

<!-- Code editor: prevent the touch keyboard from "correcting" keywords -->
<textarea autocorrect="off" autocapitalize="none" spellcheck="false"></textarea>

<!-- Username field: no autocorrect, no autocapitalise -->
<input type="text" name="username"
       autocorrect="off" autocomplete="username">

<!-- Normal prose field: autocorrect on (the default) -->
<textarea></textarea>