The HTML autocorrect attribute allows web authors to control whether autocorrection should be applied to user input in editable elements including <input>, <textarea>, and contenteditable hosts. On Windows, the touch keyboard ignores this attribute and always autocorrects words. For example, typing "truf" followed by space in an element with autocorrect="off" yields "true " instead of preserving "truf ". This feature makes Chrome's TSF integration detect and revert touch keyboard autocorrections when the focused editable element has autocorrect="off" set.
The autocorrect attribute is defined in the HTML Living Standard and applies to both form controls (<input>, <textarea>) and editing hosts (elements with contenteditable). On Android, Chrome correctly communicates this preference to the soft keyboard via EditorInfo.inputType flags. On Windows, however, TSF's InputScope interface has no autocorrect field, so the touch keyboard is unaware of the page's preference and always autocorrects. This creates a broken experience for web apps that explicitly disable autocorrection such as code editors, username/email fields, medical or legal forms, and any scenario where precise user input must be preserved. This feature fixes the gap by having Chrome detect and revert touch keyboard autocorrections at the TSF layer when autocorrect="off" is set on the focused editable element. Moreover, Autocorrect is performed only by the touch keyboard's prediction engine. Physical keyboards and traditional IMEs go through composition ranges and are unaffected. Firefox also does not honor autocorrect="off" on the Windows touch keyboard, verified that it autocorrects every time. For non-touch (physical keyboard), neither browser has autocorrected behavior.