demo · v149

Developer Input Showcase

Developer tools, code editors, and technical apps are full of fields where autocorrection is actively harmful — API keys get mangled, code identifiers get "fixed", regex special characters disappear. Each field below shows the complete recommended attribute set, with autocorrect="off" now correctly propagated to the Windows touch keyboard in Chrome 149.

8field types
4attributes shown
✓Chrome 149 fix
Username / handle high risk without fix
Autocorrection turns "jsmith3" into "j smith3" or changes capitalisation. Must be preserved exactly.
autocorrect="off" autocomplete="username" autocapitalize="none" spellcheck="false"
<input type="text" autocorrect="off" autocomplete="username" autocapitalize="none" spellcheck="false">
API key / secret token high risk without fix
Tokens contain random alphanumerics, hyphens, and underscores. Any autocorrect makes the key invalid.
autocorrect="off" autocomplete="off" autocapitalize="none" spellcheck="false"
<input type="text" autocorrect="off" autocomplete="off" autocapitalize="none" spellcheck="false">
URL / endpoint high risk without fix
Autocorrect adds spaces, capitalises "http", and mangles path segments. type="url" doesn't always suppress it on touch keyboards.
autocorrect="off" type="url" autocapitalize="none" spellcheck="false"
<input type="url" autocorrect="off" autocapitalize="none" spellcheck="false">
Code / shell command high risk without fix
Autocorrect turns const into "Const", adds curly apostrophes, and mangles variable names.
autocorrect="off" autocapitalize="none" spellcheck="false"
<textarea autocorrect="off" autocapitalize="none" spellcheck="false"></textarea>
Regex / search pattern high risk without fix
Special characters like ^, $, \d, (?: are essential. Autocorrect deletes or replaces them.
autocorrect="off" autocapitalize="none" spellcheck="false"
<input type="text" autocorrect="off" autocapitalize="none" spellcheck="false">
Technical search / filter medium risk
Log viewers, package search, file path filter. Autocorrect often adds wrong spaces or capitalises identifiers.
autocorrect="off" type="search" autocapitalize="none" spellcheck="false"
<input type="search" autocorrect="off" autocapitalize="none" spellcheck="false">
Git branch / tag / commit SHA high risk without fix
Branch names use slashes, hyphens, and lowercase only by convention. SHA hashes are purely hex — any correction breaks them.
autocorrect="off" autocapitalize="none" spellcheck="false"
<input type="text" autocorrect="off" autocapitalize="none" spellcheck="false">
Natural language message (contrast) autocorrect="on" — correct
Regular text entry should keep autocorrect on. This shows the default: no attributes means the OS keyboard corrects as expected.
no autocorrect=off
<textarea></textarea> <!-- No autocorrect attribute = autocorrect on (default) -->

Why each attribute is needed

Attribute What it controls Chrome 149 fix
autocorrect="off" Disables autocorrect suggestions from browser and OS keyboard Now propagated to Windows TSF keyboard
autocapitalize="none" Stops touch keyboards from capitalising the first letter Independent of this fix
spellcheck="false" Suppresses red-squiggle spell-check underlining Independent of this fix
autocomplete="off" Suppresses saved-value dropdown for sensitive fields Independent of this fix 
<!-- The complete attribute set for a technical developer input -->
<input type="text"
  autocorrect="off"       <!-- Chrome 149: now works on Windows touch keyboard via TSF -->
  autocapitalize="none"  <!-- Prevent first-char capitalisation -->
  spellcheck="false"     <!-- Hide red squiggles -->
  autocomplete="off"     <!-- No saved-value dropdown (for secrets) -->
>

see also

implementation reference

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