← back to v149 · service-worker-router-timing-fields
conformance · v149
v149 · 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 |
|---|---|---|---|---|
service-worker-container-exists |
navigator.serviceWorker is present (router is wired into service-worker registration). spec ↗ | exists | … | |
performance-resource-timing-supported |
PerformanceResourceTiming exists — the surface that exposes new router timing fields. spec ↗ | exists | … | |
worker-router-evaluation-start-on-prototype |
PerformanceResourceTiming.prototype has workerRouterEvaluationStart for router decision timing. spec ↗ | script | … | |
worker-cache-lookup-start-on-prototype |
PerformanceResourceTiming.prototype has workerCacheLookupStart for cache-route timing. spec ↗ | script | … | |
performance-get-entries-by-type-resource |
Performance.getEntriesByType('resource') returns entries with the new fields populated. spec ↗ | typeof | … | |
service-worker-router-matched-source-on-fetch-event |
FetchEvent (in service worker) exposes a way to inspect matched router source. spec ↗ | script | … |