← back to v134 · bounce-tracking-mitigations-on-http-cache
conformance · v134
v134 · bounce-tracking-mitigations-on-http-cache — 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 |
|---|---|---|---|---|
storage-access-api |
Storage Access API is exposed — the recommended replacement when first-party state is cleared by bounce-tracking mitigations. | typeof | … | |
has-storage-access |
document.hasStorageAccess is exposed so pages can check state after a bounce-tracking-driven clear. | typeof | … | |
clear-site-data-not-blocked-on-throw |
Fetching a URL with no body / no special header from same-origin does not throw (mitigations are silent — there is no observable error). | script | … | |
cookie-store-exposed |
cookieStore is exposed when present — pages can observe cookie-clearing side effects of mitigations. | script | … | |
no-direct-api-surface |
Bounce-tracking mitigations are a UA-internal heuristic — there is intentionally no document.bounceTrackingMitigation API to query. | script | … |