- From: Ben Kelly <notifications@github.com>
- Date: Wed, 16 Nov 2016 12:06:54 -0800
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
Received on Wednesday, 16 November 2016 20:07:28 UTC
> Client.postMessage() currently goes to navigator.serviceWorker.onmessage. This would need to still happen for service worker globals. When used from other globals we would need to fire the event at a different target. Perhaps navigator.clients.onmessage. In regards to this item, perhaps we could make the message event fire at `navigator.serviceWorker.onmessage` first and then bubble to `navigator.clients.onmessage`. This would make the new `clients.onmessage` consistently useful while still allowing back-compat with the `serviceWorker.onmessage`. -- 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/955#issuecomment-261056530
Received on Wednesday, 16 November 2016 20:07:28 UTC