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

> When @mattto approved #1274, I thought we could maintain a data structure in the browser process that tracks the clients.

Sure, the list is maintained in the browser process, but accessing that list from the renderer process is going to be async.  Unless we want to block or spin the event loop while we consult cross-process state we can't synchronously throw here.

IMO anyway.

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