← back to v136 · incorporating-navigation-initiator-into-the-http-cache-partition-key
conformance · v136
v136 · incorporating-navigation-initiator-into-the-http-cache-partition-key — 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 is exposed — the API whose cache hits are now partitioned by navigation initiator. | typeof | … | |
cache-storage-exposed |
caches (CacheStorage) is exposed — explicit cache API is unaffected by HTTP cache partitioning. | exists | … | |
request-mode-supported |
Request supports the same-origin mode flag — partitioning is orthogonal to mode semantics. | script | … | |
performance-resource-entries-still-available |
performance.getEntriesByType('resource') still surfaces resource timing — cache key changes are observable here as transferSize changes. | script | … | |
performance-navigation-type-exposed |
PerformanceNavigationTiming.type is exposed — initiator partitioning specifically affects entries with a navigate/reload type. | script | … |