← back to v138 · cache-sharing-for-extremely-pervasive-resources
conformance · v138
v138 · cache-sharing-for-extremely-pervasive-resources — conformance probe
5 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
5
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
fetch-exists |
fetch() exists — the HTTP cache layer this feature modifies is reachable from script via fetch. spec ↗ | exists | … | |
fetch-is-function |
fetch is callable; cache sharing is transparent to the API. | typeof | … | |
request-cache-modes-still-honored |
Request.cache reflects the chosen cache mode; shared cache cannot override an explicit no-store. spec ↗ | script | … | |
performance-resource-timing |
PerformanceResourceTiming is available so a page can still observe cached-resource timings (transferSize, etc.) when shared cache is used. spec ↗ | exists | … | |
transfer-size-readable |
A PerformanceResourceTiming entry exposes transferSize as a number — the primary observable for whether a fetch hit a shared cache. spec ↗ | script | … |