v149 · HTML · TSF Demo
TSF Demo
Side-by-side inputs with and without autocorrect="off". On Windows with a touch keyboard, Chrome 149 now correctly communicates the attribute via TSF — the keyboard suppresses corrections in the opted-out fields.
Platform detection
Detecting platform…
live inputs
Default — autocorrect on
<input> (no autocorrect attr)
<textarea> (no autocorrect attr)
autocorrect="off"
<input autocorrect="off">
<textarea autocorrect="off">
behaviour by version and input method
| Input method | Chrome pre-149 | Chrome 149+ |
|---|---|---|
| Physical keyboard (all OS) | Respected autocorrect="off" | Respected (unchanged) |
| macOS touch keyboard / QuickType | Respected autocorrect="off" | Respected (unchanged) |
| Android on-screen keyboard | Respected via inputmode | Respected (unchanged) |
| Windows touch keyboard (TSF) | Bug: ignored autocorrect="off" | Fixed: TSF now receives correct flags |
common use cases for autocorrect="off"
- Username / email fields — corrections mangle usernames like
j_smith99 - Password fields — already handled by
type="password", but explicitautocorrect="off"adds a second layer - Code editors — keywords, identifiers, and symbols must not be altered
- URL / slug inputs — corrections change paths and break links
- Technical / medical terminology — domain-specific terms that autocorrect "fixes" incorrectly
see also
implementation reference
Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗