- From: Jungkee Song <notifications@github.com>
- Date: Mon, 14 Dec 2015 01:49:16 -0800
- To: slightlyoff/ServiceWorker <ServiceWorker@noreply.github.com>
Received on Monday, 14 December 2015 09:49:45 UTC
If `.ready` were designed to resolve when the client got a controller, we couldn't use it for the initial client loading triggered w/o a registration and the shift + reload case (as that client will live w/o a controller for its lifetime). `controllerchange` is exactly the event to catch the client's controller (active worker) change. I think changing the behavior of `.ready` is not a good idea. Let's discuss whether we really want to add such an API. /cc @jakearchibald @slightlyoff --- Reply to this email directly or view it on GitHub: https://github.com/slightlyoff/ServiceWorker/issues/799#issuecomment-164393241
Received on Monday, 14 December 2015 09:49:45 UTC