Hey Alex! The results <https://docs.google.com/presentation/d/1wtghSYKuoASf8lKY3ghMDk5G5QquBsU-wwI4JOxL590/edit?slide=id.p#slide=id.p> Shopify got from this API indicate real improvement for users, and extending the OT would enable further experimentation by the relevant Shopify team. Beyond that, I'm now talking to other partners about potential experimentation on their end that would confirm this is the right way to go.
Cheers :) Yoav On Tue, Sep 15, 2026 at 12:20 AM Alex Russell <[email protected]> wrote: > Hey Yoav, > > I'm inclined to LGTM this, but want to understand if we have developer > feedback from the OT that has run thus far? Is it possible to summarize, > and/or maybe outline why we're doing an extension if we don't have it > (delayed partners, etc.)? > > Thanks, > > Alex > > On Sunday, September 13, 2026 at 4:00:20 AM UTC-7 Yoav Weiss wrote: > >> *Contact emails* >> [email protected] >> >> *Explainer* >> https://github.com/WICG/autofill-event?tab=readme-ov-file#autofill-event >> >> *Specification* >> https://wicg.github.io/autofill-event >> >> *Summary* >> Autofill is a key feature of the web that reduces friction for millions >> of users everyday. But getting autofill to work reliably with dynamic forms >> across multiple implementations requires jumping through many hoops. This >> feature adds an "autofill" event that would allow developers to modify >> their forms to fit the autofilled data and let the browser know when they >> have done so. >> >> *Blink component* >> Blink >> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%22> >> >> *Web Feature ID* >> Missing feature >> >> *TAG review* >> https://github.com/w3ctag/design-reviews/issues/1197 >> >> *TAG review status* >> Pending >> >> *Origin Trial Name* >> Autofill Event >> >> *Goals for experimentation* >> We want to gather real-life experience with the API, and gain insights >> into: >> * Working with the API compared to legacy methods (e.g. honeypot fields, >> autofill detection, etc) >> * Working with autofill extensions >> >> *Chromium Trial Name* >> AutofillEvent >> >> *Origin Trial documentation link* >> https://github.com/WICG/autofill-event?tab=readme-ov-file#autofill-event >> >> *WebFeature UseCounter name* >> kAutofillEvent >> >> *Risks* >> >> >> *Interoperability and Compatibility* >> *No information provided* >> >> *Gecko*: No signal ( >> https://github.com/mozilla/standards-positions/issues/1361) >> >> *WebKit*: No signal ( >> https://github.com/WebKit/standards-positions/issues/431) >> >> *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* >> >> >> *Reason this experiment is being extended* >> As Shopify experimented with the API, we got encouraging positive results >> <https://docs.google.com/presentation/d/1wtghSYKuoASf8lKY3ghMDk5G5QquBsU-wwI4JOxL590/edit?slide=id.p#slide=id.p> >> that >> convinced us that the API is worthwhile to continue pursuing. The OT >> extension would enable us to continue collect data, convince more address >> form providers to join the trial and work on advancing shipping artifacts. >> >> *Ongoing technical constraints* >> None >> >> *Debuggability* >> *No information provided* >> >> *Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, ChromeOS, Android, and Android WebView)?* >> No >> WebViews have a slightly different behavior as they don't yet support >> autofill retriggering. >> >> *Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?* >> No >> Currently the feature is only tested using browser tests. There's a >> web-driver bidi proposal to enable its testing: >> https://github.com/w3c/webdriver-bidi/pull/706/ >> We're planning to incorporate this proposal into the feature's >> specification. >> >> *Flag name on about://flags* >> *No information provided* >> >> *Finch feature name* >> AutofillEvent >> >> *Requires code in //chrome?* >> True >> >> *Tracking bug* >> https://issues.chromium.org/issues/466333215 >> >> *Estimated milestones* >> Origin trial desktop first 147 >> Origin trial desktop last 152 >> Origin trial extension 1 end milestone 158 >> Origin trial Android first 147 >> Origin trial Android last 152 >> >> *Link to entry on the Chrome Platform Status* >> https://chromestatus.com/feature/5137581018841088?gate=5201831641874432 >> >> *Links to previous Intent discussions* >> Intent to Prototype: >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOmohSKGDT5iwAZXt-CyR5jSh5Ohr8PJCwsf_KMHEyF_s6xXZQ%40mail.gmail.com >> Intent to Experiment: >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOmohS%2B4anwtf7mz4-Ee7gH%2BWq3h-dwdPHmQnAGLgjN5TqPwig%40mail.gmail.com >> >> >> 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/CAOmohSJavs7Doona4WKq38T0EYMXtFdEeNWYin-dVogtMU35Sw%40mail.gmail.com.
