← back to v131 · fedcm-as-a-trust-signal-for-the-storage-access-api
conformance · v131
v131 · fedcm-as-a-trust-signal-for-the-storage-access-api — 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 |
|---|---|---|---|---|
identitycredential-exposed |
IdentityCredential is exposed for FedCM sign-in results. spec ↗ | exists | … | |
credentials-get-is-function |
navigator.credentials.get is the FedCM entry point that establishes the trust signal. spec ↗ | typeof | … | |
request-storage-access-exposed |
Document.requestStorageAccess is exposed for storage access requests that can consume a FedCM trust signal. spec ↗ | typeof | … | |
has-storage-access-exposed |
Document.hasStorageAccess is exposed for checking current storage access state. spec ↗ | typeof | … | |
fedcm-get-returns-promise |
Calling navigator.credentials.get with identity options returns a Promise and can be aborted. spec ↗ | script | … | |
requeststorageaccess-returns-promise |
requestStorageAccess returns a Promise even when approval depends on policy or prior trust. spec ↗ | script | … |