← back to v145 · device-bound-session-credentials
conformance · v145
v145 · device-bound-session-credentials — 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 |
|---|---|---|---|---|
fetch-exists |
fetch is the surface DBSC operates through — the server signals session credential binding via response headers. | typeof | … | |
subtle-crypto-exists |
crypto.subtle is exposed — DBSC relies on the user agent generating a device-bound key pair via the WebCrypto primitives. | exists | … | |
secure-context-required |
DBSC is a secure-context-only feature; isSecureContext must be observable to script. | exists | … | |
cookie-store-exists |
CookieStore is exposed — DBSC's bound sessions interact with the cookie surface used by the document. | exists | … | |
permissions-policy-exists |
FeaturePolicy / Permissions Policy mechanism (document.featurePolicy or document.permissionsPolicy) underpins DBSC's gating. | script | … |