- From: Ben Kelly <notifications@github.com>
- Date: Thu, 25 Aug 2016 06:39:43 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
Received on Thursday, 25 August 2016 13:40:12 UTC
> @wanderview maybe you are right. Anyway, this all seems like a major breaking change. Well, yes. Removing `ServiceWorker.postMessage()` is probably (?) too breaking. I was just lamenting that it ties our hands in this issue and perhaps may not really be needed. Anyway, from an implementation point of view I don't think Mozilla will be pursuing multiple SW thread instances right now. If its something other browser vendors strongly want then I'd like to see more of a proposal about how to address web compat issues. Perhaps a first step could be getting use counter information for `ServiceWorker.postMessage()` from the window. @jakearchibald does chrome collect that today? -- 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/756#issuecomment-242389596
Received on Thursday, 25 August 2016 13:40:12 UTC