v149 · Forms · demo

Autocorrect Tester

Chrome 149 correctly respects autocorrect="off" on Windows touch keyboards via TSF. Type into the five inputs below and observe which corrections are applied.

Five-input comparison

Type a deliberately misspelled word like teh or hte into each input and watch if the browser corrects it.

(1) autocorrect="on"

autocorrect="on"
spellcheck="true"

(2) autocorrect="off" ← Chrome 149

autocorrect="off"
spellcheck="false"

(3) spellcheck="false" only

spellcheck="false"

(4) autocomplete="off"

autocomplete="off"

(5) inputmode="none"

inputmode="text"
(no autocorrect attr)

Keyboard event log

Events will appear as you type above…

Windows TSF behavior (Chrome 149)

TSF (Text Services Framework) is Windows' system-level text input API. Before Chrome 149, autocorrect="off" was ignored by TSF on touch keyboards. Chrome 149 fixes this by passing the attribute to the TSF interface layer.

autocorrect="on" (or absent)TSF sends corrections

autocorrect="off"Chrome 149: TSF corrections suppressed ✓

autocorrect="off" pre-Chrome 149TSF still sent corrections (bug)

spellcheck="false" onlySquiggles off, but TSF may still correct

type="password"Always suppressed by browser

inputmode="none"Keyboard not shown — N/A

Live attribute probe

Input (2) autocorrect attr—

Input (2) spellcheck attr—

document.activeElement—

Current input value length—

Recommended password pattern

For password and sensitive inputs, combine all three attributes to ensure no browser or system-level correction:

<input
  type="password"
  autocorrect="off"
  autocomplete="new-password"
  spellcheck="false"
  autocapitalize="off"
>

implementation reference

Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗