tree 14b7e5eab987875e422f8e56521172660eb4fb47
parent 319699eab9ce7520797885e947604a8dde647867
author Noam Rosenthal <noamr@users.noreply.github.com> 1634031177 +0300
committer GitHub <noreply@github.com> 1634031177 +0300
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJhZVZJCRBK7hj4Ov3rIwAADHYIAI73FQ0S8U5xoENGLspVzzCR
 ZqIZAnJcpwhs2YigljviQKv1HwcYTlcW8KKmSu5J147j753zIHavWEDavxZ5DBFJ
 y6p5oMh2cIfwwn1rQwWrnLNklk5bxc/5j/DoUQFXO0nUzxxJqZH1jKyYivqEpBuh
 ncD8c3Z9p64Pw7gGXhJwLkxMt1N/W7/u8BHG3Ij+X/qJ2hcWalrvAF4sZxNTGRLD
 MdKlP/ndmfShZFwYK9e53J3UOS9gxqZ/xLujI1I/Ylw7cuO8B7rHjHh1ChxbR88K
 3XUKZHxrykcar4cJ1T5PdrrTNGdn4gFAoay2QwPcP7U5MJSGrWQWNV0kjiS0xJQ=
 =M7lq
 -----END PGP SIGNATURE-----
 

[navigation-timing]: Test fine-grained Service Worker timing (#31187)

* [navigation-timing]: Test fine-grained Service Worker timing

Mark the timing inside the service worker (and adjust by timeOrigin), to
make sure the timing reported to Navigation Timing correspond with the
milestones specified in
https://w3c.github.io/ServiceWorker/#service-worker-timing.

The four relevant milestones which should be in order:
- PerformanceNavigationTiming.workerStart
- Finish the activation event
- PerformanceNavigationTiming.fetchStart
- Handling the Fetch event in the worker

This is to ensure that the difference between workerStart and fetchStart
measures the delay caused by service worker activation.

See https://github.com/w3c/navigation-timing/issues/148

* Use step_timeout

* Remove unnecessary timeouts