- From: Dave Tapuska <notifications@github.com>
- Date: Mon, 15 Jul 2019 12:36:09 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 15 July 2019 19:36:31 UTC
I don't really know the answers.. > Is it a nefarious trick they can use to get their client unfrozen? It may be subject to UA policies of freezing and unfreezing. I know there was some discussions in Chrome if the browser should periodically unfreeze the client. > Or is it expected that such postMessage() calls will hasten the discarding of the client? In Chrome, postMessages may cause your own death sooner not necessarily discarding the client. But again there was some thought that a client should transition to discarded if it gets too many postMessages queued. Do you expect these to be covered in the Service Worker spec, I'd think these should be described maybe in the page lifecycle spec because you could postMessage or broadcastChannel to a frame with window handles or message channels so it isn't directly tied to ServiceWorkers. -- 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/1442#issuecomment-511539586
Received on Monday, 15 July 2019 19:36:31 UTC