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

@domenic, thanks for the information. Good to be aware of for future discussion.

> Sure, the list is maintained in the browser process, but accessing that list from the renderer process is going to be async.

Ah.. right. This call starts from the renderer. I was confused myself we were on the browser process at the beginning.

I'll make another PR to address this issue and close the PR in WPT.

I'm thinking of getting the associated service worker client and returning if it doesn't exist, which would be analogous to https://cs.chromium.org/chromium/src/content/browser/service_worker/service_worker_version.cc?type=cs&q=ServiceWorkerVersion::PostMessageToClient&l=1155.

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