LGTM2

On Fri, May 22, 2026 at 10:00 AM Daniel Bratell <[email protected]> wrote:

> LGTM1
>
> /Daniel
> On 2026-05-22 09:33, Chromestatus wrote:
>
> *Contact emails*
> [email protected]
>
> *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
> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EEditing%3EIME%22>
>
> *Web Feature ID*
> autocorrect <https://webstatus.dev/features/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*
>
>
> *Interoperability and Compatibility*
> The feature is supported in Firefox and Safari, so I don't think there is
> any interoperability risk on exposing this feature.
> https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/autocorrect
>
> *Gecko*: Shipped/Shipping (
> https://bugzilla.mozilla.org/show_bug.cgi?id=1927977)
> https://www.firefox.com/en-US/firefox/136.0/releasenotes/
>
> *WebKit*: Shipped/Shipping (
> https://webkit.org/blog/16301/webkit-features-in-safari-18-2)
> https://webkit.org/blog/15860/release-notes-for-safari-technology-preview-203/
>
> *Web developers*: No signals
>
> *Other signals*:
>
> *WebView application risks*
>
> Does this intent deprecate or change behavior of existing APIs, such that
> it has potentially high risk for Android WebView-based applications?
> *No information provided*
>
>
> *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.
>
> *Is this feature fully tested by web-platform-tests
> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?*
> 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
>
> This intent message was generated by Chrome Platform Status
> <https://chromestatus.com>.
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a1006d5.050a0220.38d8a1.00db.GAE%40google.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a1006d5.050a0220.38d8a1.00db.GAE%40google.com?utm_medium=email&utm_source=footer>
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/0b2c4068-b58c-48c2-b877-8f474a36f7a5%40gmail.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/0b2c4068-b58c-48c2-b877-8f474a36f7a5%40gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOmohSLTfwknD16xRsz4wBOv5mAZuetKoqgQW4-zLs%2Bve%2BZC3w%40mail.gmail.com.

Reply via email to