Contact emails
jfern...@igalia.com
Specification
https://html.spec.whatwg.org/multipage/interaction.html#autocorrection
Summary
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. The feature makes the 'autocorrect' attribute to be exposed to web authors.
Blink component
Blink>Editing>IME
Web Feature ID
autocorrect
Motivation
The 'autocorrect' HTML attribute has been implemented long ago, but since it's not defined in any exported IDL, websites fail to detected it as supported.
Initial public proposal
No information provided
TAG review
No information provided
TAG review status
Not applicable
Goals for experimentation
None
Risks
Debuggability
No information provided
Will this feature be supported on all six Blink platforms
(Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
Yes
The platform support varies considerably, given that this feature depends heavily on the underlying OS capabilities for spell checking and IME functionalities.
Yes
The Web Platform Tests coverage is quite limited in terms of functionality due to the high dependency on the platform's capabilities.
There are a few tests to check the IDL correctness and some basic spec conformance.
https://wpt.fyi/results/html/editing/editing-0/autocorrection/autocorrection.html?label=experimental&label=master&aligned
https://github.com/web-platform-tests/wpt/blob/master/html/editing/editing-0/autocorrection/autocorrect-off-touch-keyboard-manual.html
Flag name on about://flags
No information provided
Finch feature name
No information provided
Non-finch justification
No information provided
Rollout plan
Will ship enabled for all users
Requires code in //chrome?
False
Tracking bug
https://issues.chromium.org/issues/40871769
Estimated milestones
| Shipping on desktop | 151 |
| Shipping on Android | 151 |
| Shipping on WebView | 151 |
| Shipping on iOS | 151 |
Anticipated spec changes
Open questions about a feature may be a source of future web compat or
interop issues. Please list open issues (e.g. links to known github
issues in the project for the feature specification) whose resolution
may introduce web compat/interop risk (e.g., changing to naming or
structure of the API in a non-backward-compatible way).
No information provided
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/6264645053710336?gate=4718478864023552