Re: [w3c/ServiceWorker] clarify that Client "creation order" means when reserved Client created (#1078)

Sorry about the confusion first of all. I edited my comment above using a strikethrough: s/earlier/later/. Basically, I was concerned about the case where `client.reserved == true` client comes before `client.reserved == false` client.

I think I'd have to dig into the definition of focused, focusable area and such more, but this is the scenario I was thinking about:

SW A, B, and C for the same origin with different scopes are running. SW C running matchAll() captures the following state:
1. SW A calls windowClient.navigate(url).
1. Reserved client for A created during navigate A.
1. SW B calls clients.openWindow(url).
1. Reserved client for B created during navigate B.
1. After fetching the resource for navigate B, reserved client for B is fully transferred to an execution ready client. (I.e., the environment settings object is created.)
1. Navigate A's still fetching resource without its environment settings object and global created.

The matchAll() from SW C returns [ .. , windowClient_A, windowClient_B, ..] even though windowClient_A is still reserved and windowClient_B is execution ready.

-- 
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/1078#issuecomment-282456543