← back to v133 · storage-access-headers
conformance · v133
v133 · 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 new headers are server-side activation of the same machinery. | script | … | |
document-hasstorageaccess-exists |
Document.prototype.hasStorageAccess is exposed. | script | … | |
requeststorageaccess-returns-promise |
requestStorageAccess returns a Promise. | script | … | |
hasstorageaccess-returns-promise |
hasStorageAccess returns a Promise. | script | … | |
fetch-supported-for-header-roundtrip |
fetch is exposed; it is the surface that round-trips the Sec-Fetch-Storage-Access / Activate-Storage-Access headers. | typeof | … |