← back to v154 · ask-before-http-on-by-default
conformance · v154
v154 · ask-before-http-on-by-default — 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 |
|---|---|---|---|---|
issecurecontext-is-boolean |
window.isSecureContext is exposed as a boolean — the page-observable signal Ask-before-HTTP steers toward. spec ↗ | typeof | … | |
https-page-is-secure-context |
A page delivered over https: is a secure context (vacuously true when this suite runs on a non-https page). spec ↗ | script | … | |
loopback-http-is-trustworthy |
An http: page on loopback (localhost / 127.0.0.1 / [::1]) is still a secure context — the reason Balanced mode never warns on local development (vacuously true off loopback). spec ↗ | script | … | |
public-http-is-not-secure-context |
A plaintext http: page on a non-loopback host must NOT be a secure context — the state the Chrome 154 warning asks about (vacuously true when this suite runs elsewhere). spec ↗ | script | … | |
balanced-mode-interstitial |
Navigating to a public HTTP-only site in Chrome 154+ shows the full-page 'doesn't support a secure connection' warning before any plaintext request is sent. spec ↗ | manual | … | |
httpsonlymode-policy-enforcement |
The HttpsOnlyMode enterprise policy (allowed / disallowed / force_enabled / force_balanced_enabled) controls the mode, and HttpAllowlist exempts named hosts. spec ↗ | manual | … |