See https://www.w3.org/TR/resource-timing-2/#dom-performanceresourcetiming-workerstart
<rdar://problem/35391187>
Also see https://github.com/w3c/resource-timing/issues/118 and https://github.com/w3c/resource-timing/issues/110
I checked what other browsers do / if they implement PerformanceResourceTiming workerStart. Steps: 1. Open <https://mdn.github.io/sw-test/> 2. Debug Service Worker 3. js> fetch("/sw-test/style.css") 4. js> performance.getEntries() Chrome Canary (65.0.3311.0) => Has ResourceTiming entries => workerStart appears to always be 0 Firefox Nightly (59.0a1 (2018-01-04)) => Does not have ResourceTiming entries
Pull request: https://github.com/WebKit/WebKit/pull/1348
Committed r295518 (251523@main): <https://commits.webkit.org/251523@main> Reviewed commits have been landed. Closing PR #1348 and removing active labels.