Re: [w3c/ServiceWorker] should clients.claim() control reserved Clients? (#1090)

> I changed this part of the spec. It's nothing but moving the active service worker internal slot from the previous concept of service worker client (an environment settings object) to environment because we needed to attach a controller before the actual environment settings object/global object/document are created.

I think even further back the controlled windows has ServiceWorkerRegistration objects associated.  Gecko was written to match and I wrote a bug to switch to the same model used by the spec:

https://bugzilla.mozilla.org/show_bug.cgi?id=1247055

But as comment 3 points out there, though, this is handled down in the Activate algorithm.  Its now step 7.1 here:

https://w3c.github.io/ServiceWorker/#activation-algorithm

```
7. For each service worker client client who is using registration:
  1. Set client’s active worker to registration’s active worker.
```

I believe a controlled reserved client should count as "using registration" in step 7 here.

-- 
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/1090#issuecomment-288612826