← back to v148 · connection-allowlists
conformance · v148
v148 · connection-allowlists — 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-is-function |
Connection Allowlists gates fetch(); fetch itself remains the entry point. spec ↗ | typeof | … | |
header-name-stable |
Document Policy / equivalent header parsing remains exposed on Response objects. spec ↗ | script | … | |
fetch-blocked-rejects |
A fetch to a disallowed origin must reject with a TypeError, mirroring CSP block semantics. spec ↗ | script | … | |
worker-fetch-also-covered |
Workers expose fetch; the allowlist applies to worker-initiated fetches too. spec ↗ | script | … | |
policy-controlled-feature-name |
document.featurePolicy / featureNames continues to enumerate policy-controlled features used to enforce allowlists. spec ↗ | script | … |