Re: [w3c/ServiceWorker] Client.postMessage() throwing for unloaded client is problematic (#1291)

I see. `port.postMessage` just returns when the target is unavailable. (Step 6 of https://html.spec.whatwg.org/#dom-messageport-postmessage.) I'm not sure though we had had any specific intent to make `Client.postMessage` throw in the current text.

@jakearchibald, do you recall anything about it?

>From https://github.com/w3c/web-platform-tests/pull/10153#issuecomment-375736919,

> @jungkees Also, how is the implementation capable of synchronously throwing here? The client and its ServiceWorkerContainer may be in another process.

When @mattto approved https://github.com/w3c/ServiceWorker/pull/1274, I thought we could maintain a data structure in the browser process that tracks the clients.

/cc @aliams @cdumez

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