- From: Marijn Kruisselbrink <notifications@github.com>
- Date: Mon, 03 Apr 2017 23:28:06 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 4 April 2017 06:28:39 UTC
Not entirely related to this PR, but the spec for ServiceWorker.postMessage looks not entirely correct. We call "Run Service Worker", which in parallel creates the workers global object, yet postMessage in the next step tries to synchronously access that global (which hasn't been created yet at that point). It seems instead postMessage should synchronously serialize the message, and then queue a task on the worker to actually deliver the message event after the worker has started up? -- 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/pull/1102#issuecomment-291405609
Received on Tuesday, 4 April 2017 06:28:39 UTC