← back to v147 · device-bound-session-credentials
conformance · v147
v147 · device-bound-session-credentials — 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 |
|---|---|---|---|---|
dbsc-fetch-still-works |
fetch() — the network surface DBSC layers onto — is still exposed. | typeof | … | |
secure-context-required |
DBSC is a secure-context feature: window.isSecureContext is defined. | exists | … | |
cookie-store-available-for-binding |
cookieStore — used to observe the bound short-lived cookies — is available in secure contexts. spec ↗ | script | … | |
credential-management-api |
navigator.credentials is available — DBSC integrates with Credential Management. spec ↗ | exists | … | |
dbsc-header-observable-via-fetch |
Fetch responses expose a headers interface so the Sec-Session-Registration response header can be observed. spec ↗ | typeof | … | |
dbsc-no-js-constructor |
DBSC is a network-layer feature with no JS-visible registration API — no global DBSC constructor is exposed. spec ↗ | script | … |