← back to v147 · webrequest-securityinfo-in-controlled-frame
conformance · v147
v147 · webrequest-securityinfo-in-controlled-frame — 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 |
|---|---|---|---|---|
iwa-gated-webrequest-hook |
In non-IWA pages chrome.webRequest may be absent; when exposed, onHeadersReceived.addListener is the SecurityInfo hook. spec ↗ | script | … | |
non-iwa-fallback-is-explicit |
A regular page without chrome.webRequest must treat SecurityInfo as unavailable rather than probing unrelated APIs. spec ↗ | script | … | |
securityinfo-secure-fingerprint-shape |
A usable SecurityInfo payload has state='secure', a certificate descriptor, and a 64-hex SHA-256 fingerprint. spec ↗ | script | … | |
missing-securityinfo-blocks-pinning |
If extraInfoSpec does not request securityInfo/securityInfoRawDer, details.securityInfo is absent and the app must not pin. spec ↗ | script | … | |
rawder-option-preserves-fingerprint |
A securityInfoRawDer-style payload can include raw certificate bytes while still exposing the fingerprint used for pinning. spec ↗ | script | … |