← back to v146 · cache-sharing-for-extremely-pervasive-resources
conformance · v146
v146 · cache-sharing-for-extremely-pervasive-resources — 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 |
|---|---|---|---|---|
resource-timing-api-available |
The Resource Timing API is the observable surface for cache-hit behaviour — performance.getEntriesByType('resource') must be exposed. | typeof | … | |
performance-resource-timing-transfersize |
PerformanceResourceTiming exposes transferSize, which a cached pervasive resource reports as 0 (or near-0) on hit. | script | … | |
fetch-api-available |
The fetch API is available to issue requests that may be served from the shared pervasive-resource cache. | typeof | … | |
cache-storage-api-distinct |
The CacheStorage interface (window.caches) remains a separate, scriptable cache — unrelated to the HTTP cache partition that pervasive sharing modifies. | exists | … | |
performance-navigation-type-reload |
performance.navigation entries expose 'type' so demos can distinguish a fresh load from a reload when illustrating cache behaviour. | script | … | |
no-cache-partition-js-api |
No script-exposed API lets a page read or set HTTP cache partition keys — the pervasive-resource allowlist is browser-managed, not web-controllable. | script | … |