[w3c/ServiceWorker] postMessage() to a reserved client throws (#1035)

While discussing https://github.com/w3c/ServiceWorker/issues/1031#issuecomment-267948728, I noticed that `client.postMessage()` to a reserved client in the current spec throws as the destination (`ServiceWorkerContainer`) object shouldn't have been created yet. I think we may need a separate message queue to hold the messages while a client is in the reserved state, and re-queue them to the client message queue of the `ServiceWorkerContainer` object when it's created.

-- 
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/1035