← back to v130 · storage-access-headers
conformance · v130
v130 · storage-access-headers — 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 |
|---|---|---|---|---|
document-requeststorageaccess-exists |
Document.prototype.requestStorageAccess remains exposed; the headers activate the same storage access machinery. spec ↗ | script | … | |
document-hasstorageaccess-exists |
Document.prototype.hasStorageAccess is exposed for checking current storage access state. spec ↗ | script | … | |
requeststorageaccess-returns-promise |
requestStorageAccess returns a Promise even when the request later rejects. spec ↗ | script | … | |
hasstorageaccess-returns-promise |
hasStorageAccess returns a Promise for the current document. spec ↗ | script | … | |
fetch-header-channel-available |
fetch is exposed as the request channel that observes Sec-Fetch-Storage-Access and Activate-Storage-Access. spec ↗ | typeof | … |