Re: [w3c/ServiceWorker] Teach ExtendableMessageEvent to work with origins. (PR #1821) from Yoshisato Yanagisawa on 2026-03-11 (public-webapps-github@w3.org from March 2026)

From: Yoshisato Yanagisawa <notifications@github.com>
Date: Tue, 10 Mar 2026 23:46:03 -0700
To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/ServiceWorker/pull/1821/c4036896153@github.com>

yoshisatoyanagisawa left a comment (w3c/ServiceWorker#1821)

Thanks for the update. To ensure full parity with the changes made to `MessageEvent` in whatwg/html#12235, I was looking for the "extract an origin" steps for `ExtendableMessageEvent`.

Since `ExtendableMessageEvent` doesn't inherit from `MessageEvent`, we'll need an explicit definition to support the `Origin.from()` API. Should we add a sentence similar to the one in the [HTML spec](https://html.spec.whatwg.org/#the-messageevent-interface:extract-an-origin) here as well?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/pull/1821#issuecomment-4036896153
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/ServiceWorker/pull/1821/c4036896153@github.com>

Received on Wednesday, 11 March 2026 06:46:07 UTC