Bug 179377
| Summary: | Implement PerformanceResourceTiming.workerStart in ServiceWorkers | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ryosuke Niwa <rniwa> |
| Component: | WebKit Misc. | Assignee: | youenn fablet <youennf> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | beidson, cdumez, joepeck, webkit-bug-importer, youennf |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Ryosuke Niwa
See https://www.w3.org/TR/resource-timing-2/#dom-performanceresourcetiming-workerstart
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/35391187>
Ryosuke Niwa
Also see https://github.com/w3c/resource-timing/issues/118 and https://github.com/w3c/resource-timing/issues/110
Joseph Pecoraro
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
youenn fablet
Pull request: https://github.com/WebKit/WebKit/pull/1348
EWS
Committed r295518 (251523@main): <https://commits.webkit.org/251523@main>
Reviewed commits have been landed. Closing PR #1348 and removing active labels.