- From: Sam Goto <notifications@github.com>
- Date: Tue, 15 Sep 2026 13:10:34 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/1169/5687407011@github.com>
samuelgoto left a comment (w3ctag/design-reviews#1169) While this review is already closed, I figured you all would appreciate a report on the progress we have been making. Since my last message in June 16th, Chrome started an Origin Trial in July 8th: https://developer.chrome.com/blog/email-verification-protocol-origin-trial So far the results have been really encouraging, both in terms of user satisfaction (UXR and metrics are looking good) as well as developer adoption / activation. I think we have done a reasonable job at API design, but it is a pretty wide design space (e.g. using the [HTML autocomplete API](https://github.com/WICG/email-verification#21-evt-request) and introducing a `nonce` parameter to `input`, how it [participates in form submission](https://github.com/WICG/email-verification/issues/42), as well as things like how it intersects with [shadow DOM](https://developer.chrome.com/blog/email-verification-protocol-origin-trial)). I'll keep this thread posted as the origin trial progresses and comes to an end (we are expecting before the end of the year) and moves onto an intent to ship, just wanted to report back and give a heads up on the where things are going. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1169#issuecomment-5687407011 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1169/5687407011@github.com>
Received on Tuesday, 15 September 2026 20:10:39 UTC