- From: Jungkee Song <notifications@github.com>
- Date: Tue, 31 Mar 2015 01:48:31 -0700
- To: slightlyoff/ServiceWorker <ServiceWorker@noreply.github.com>
Received on Tuesday, 31 March 2015 08:48:55 UTC
> however (just in case it's not clear) that r.active can be an "activating" SW, which would not receive these events until activation succeeds. `controllerchange` events' target is ServiceWorkerContainer objects. So, it doesn't have to do with the worker's state I guess? > Activate's step 10: "For each service worker client client whose active worker is not null..." seems wrong. It should say "for clients already associated with the registration..." Reading that is what caused me to think the controllerchange naming is wrong. The state where client's active worker is not null means the client is currently being controlled. So I think the two in your comment above have the same meaning. --- Reply to this email directly or view it on GitHub: https://github.com/slightlyoff/ServiceWorker/issues/659#issuecomment-87997988
Received on Tuesday, 31 March 2015 08:48:55 UTC