Respect autocorrect=off for Windows touch keyboard in TSF

concepts

1. TSF Demo

   Live inputs with and without autocorrect="off". On Windows with a touch keyboard, the Chrome 149 fix means the TSF-backed keyboard no longer auto-corrects in fields where the attribute is set.

2. Attribute Reference

   Full reference for autocorrect, which elements support it, how it interacts with autocomplete, spellcheck, and inputmode, and what TSF is.

3. Input Attribute Tester

   Quick-reference grid of all text-input correction attributes with live inputs for each combination. Focus any field to see which attributes are active; test on Windows touch keyboard to verify Chrome 149's TSF fix propagates autocorrect="off" correctly.

4. Autocorrect Tester

   Side-by-side inputs with autocorrect="on" vs autocorrect="off" across different input types (text, search, password, textarea). A TSF flag table shows which Windows keyboard signals Chrome 149 now sends correctly. Type the same words in each field and verify the Chrome 149 fix on Windows touch keyboard.

5. Form Field Audit

   Scan a sample form and flag every field whose type logically warrants autocorrect="off" but doesn't have it set. Each field gets a verdict (correct / review / missing) with the recommendation reason. Shows how Chrome 149's TSF fix makes these audits actionable — fields previously ignored the attribute on Windows touch keyboards.

6. Developer Input Showcase

   Eight real developer-tool input types — username, API key, URL, code editor, regex, search, git branch, and natural language (contrast) — each with the complete recommended attribute set: autocorrect="off", autocapitalize="none", spellcheck="false". Live fields for each type let you confirm that Chrome 149's TSF fix prevents the Windows keyboard from mangling technical content.

   Live inputs Developer UX Best practices

why it shipped

The autocorrect attribute tells the browser's spell-check and autocorrect systems not to alter user input in marked fields. It's commonly set on username fields, code editors, URL inputs, and technical fields where correction is harmful. On Windows, Chrome communicates with the OS touch keyboard through the Text Services Framework (TSF) — a layer that mediates IME, autocorrect, and autocomplete suggestions. Chrome 149 closes a gap where the TSF bridge wasn't propagating the autocorrect="off" signal, so the Windows keyboard would still inject corrections.

the change

<!-- Always opted out of autocorrect — Chrome 149 now also
     communicates this to the Windows touch keyboard via TSF -->

<!-- Username: never autocorrect -->
<input type="text" name="username" autocorrect="off" autocomplete="username">

<!-- Code field: preserve exact input -->
<textarea autocorrect="off" spellcheck="false"></textarea>

<!-- Search: corrections often unhelpful for technical queries -->
<input type="search" autocorrect="off">

<!-- Default (no attribute): autocorrect enabled as before -->
<input type="text" name="message">

references

• ChromeStatus entry
• MDN — autocorrect attribute
• Microsoft Docs — Text Services Framework