Opinions about exposing the 'autocorrect' HTML global attribute

10 views
Skip to first unread message

Javier Fernandez

unread,
Nov 4, 2025, 5:42:27 AMNov 4
to blink-api-ow...@chromium.org, Koji Ishii, Dave Tapuska
Hi,

Chrome is the only major browser not exposing the 'autocorrect' HTML
attribute, according to the wpt.fyi dashboard [1][2]; there is in fact
an issue [3] filed in WPT interop repo. I've been discussing this with
Koji, in order to get information about the implementation status of
this feature. As far as I understand, it's partially implemented but
only for Mac platforms, despite some bugs related to the not being
case-insensitive.

Just to give more context, when the PR for the HTML spec had been
discussed, chrome expressed support [4] and described its partial
support back then.

So the question is, would Chrome be willing to expose the 'autocorrect'
attribute despite its platform-dependent functionality ? As far as I
know, both FF and Safari are already exposing it under such
circumstances. Additionally, I believe the 'autocomplete' attribute is
exposed already and its functionality also depends on the specific OS
capabilities.

I understand this would require a formal I2S request, but I'd like to
have some early feedback about the mac-only implementation issue.

Thanks.

-- javi


[1]
https://wpt.fyi/results/html/dom/idlharness.https.html%3Finclude%3DHTML.%2B?label=master&label=experimental&aligned
[2]
https://wpt.fyi/results/html/editing/editing-0/autocorrection/autocorrection.html?label=master&label=experimental&aligned
[3] https://github.com/web-platform-tests/interop/issues/1155
[4] https://github.com/whatwg/html/issues/3595#issuecomment-378696991

Rick Byers

unread,
Nov 4, 2025, 11:33:39 AM (14 days ago) Nov 4
to Javier Fernandez, Daniel Clark, si...@microsoft.com, Anupam Snigdha, blink-api-ow...@chromium.org, Koji Ishii, Dave Tapuska
Thanks for working on this Javier! I don't see any reason why we wouldn't want to match the other browsers here. I appreciate that the OS behavior is not fully under our control, that doesn't seem to me like a reason NOT to ship this API.

This might mainly be a question though for +editing/OWNERS - any concerns?

Rick

--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-d...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/7ab1495d-f0af-4da0-9de9-a9184a49a1a0%40igalia.com.
Reply all
Reply to author
Forward
0 new messages