Re: [w3c/ServiceWorker] Maintain timing for worker start/ready, for navigation requests. (#1575)

I've refactored the PR, I agree that it makes much more sense to associate the info with the response rather than with the worker.
https://github.com/w3c/navigation-timing/pull/143 is the navigation timing PR that shows how this info is going to be used. To complete the picture, we would need to modify two additional specs:

- FETCH would have to send SW-FETCH the `crossOriginIsolatedCapability` as the second argument.
- HTML would have to send the response's `service worker timing` when creating the navigation timing entry.

There are probably more ways to accomplish the same results, I went with the way that made the most sense to me but I'm open to refactor given an alternative approach.

-- 
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/1575#issuecomment-817279786