← back to v151 · resource-timing-add-spec-compliant-service-worker-router-timing-fields
conformance · v151
v151 · resource-timing-add-spec-compliant-service-worker-router-timing-fields — conformance probe
6 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
6
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
performance-resource-timing-defined |
PerformanceResourceTiming is exposed on the global — the carrier for the new router-source fields. | exists | … | |
workerMatchedRouterSource-on-prototype |
PerformanceResourceTiming.prototype exposes a workerMatchedRouterSource accessor as defined in the W3C Resource Timing spec PR #415. spec ↗ | script | … | |
workerFinalRouterSource-on-prototype |
PerformanceResourceTiming.prototype exposes a workerFinalRouterSource accessor. spec ↗ | script | … | |
performance-observer-supports-resource |
PerformanceObserver can subscribe to entries of type 'resource'; this is required to observe router-source values on real navigations. | script | … | |
router-source-fields-are-string-typed |
On a real resource entry, the new fields are typed as string (DOMString getters). On entries where the request didn't go through a SW router, they may be empty strings. spec ↗ | script | … | |
service-worker-api-available |
navigator.serviceWorker is exposed — required for the static router that produces these timing values. | exists | … |