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

I don't think this is relevant to the current bug thread, but I wanted to point out that that is not quite the general principle these days. In particular messages that cannot be delivered because of deserialization errors (such as crossing process boundaries while passing a SharedArrayBuffer) are currently specced to generate a messageerror event _at the destination_. (We talked a bit about signaling back to the source, but that's tricky, and the whole discussion was light on use cases, so it was deferred.)

Just something to remember when talking about the model of how postMessage deals with errors.

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