- From: Sam Goto <notifications@github.com>
- Date: Tue, 16 Jun 2026 11:52:59 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 16 June 2026 18:53:03 UTC
samuelgoto left a comment (w3ctag/design-reviews#1169) > We'll follow your guidance and take the protocol/backend to the IETF (and the html/frontend somewhere in the W3C and/or possibly to the WHATWG), which we'll report back on this thread as it goes along. Just to report back on this thread, @dickhardt has already been engaging at the IETF and is starting to kick off the process. Here is a draft of the spec: https://dickhardt.github.io/email-verification/draft-hardt-email-verification.html. We'll keep this thread up to date as the IETF process goes along. We broke the spec into two parts, and the browser integration parts (e.g. integration with autofill and form submission) are still going to go through the WICG/W3C process: https://github.com/WICG/email-verification https://wicg.github.io/email-verification/ For visibility, chrome is also starting an origin trial, starting in M150: https://groups.google.com/a/chromium.org/g/blink-dev/c/Vp1w1u6rYjE -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1169#issuecomment-4722251412 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1169/4722251412@github.com>
Received on Tuesday, 16 June 2026 18:53:03 UTC