← back to v135 · device-bound-session-credentials
conformance · v135
v135 · 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 exposed — DBSC operates over normal HTTP requests, no new JS API. spec ↗ | typeof | … | |
sec-session-headers-allowed-on-headers |
Headers permits Sec-Session-* names so server-sent registration headers can be inspected on Response. spec ↗ | script | … | |
subtlecrypto-available |
crypto.subtle is exposed — DBSC uses platform-bound keys but JS can still feature-detect WebCrypto. spec ↗ | exists | … | |
cookies-still-accessible-via-document |
document.cookie remains accessible — DBSC interacts with session cookies. spec ↗ | script | … | |
request-credentials-include-supported |
Request supports credentials: 'include' — required to carry the DBSC-protected cookie. spec ↗ | script | … |