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

> drop the message silently

Would this be trying to get the destination and returning if the target doesn't exist? Or just queuing a task for the event and the task failing to find a target in the content process?

I think [`port.postMessage`](https://html.spec.whatwg.org/#dom-messageport-postmessage) step 6 is doing the former based on the state it keeping in the browser process (not crossing the process boundary at the time of the call). Then, it won't cover the case where the target port has been nullified in the content process.

Do you expect we have a similar behavior for `client.postMessage`?

-- 
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-376057261