← back to v142 · local-network-access-restrictions
conformance · v142
v142 · local-network-access-restrictions — 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 |
|---|---|---|---|---|
secure-context |
The local-network-access permission is restricted to secure contexts. | script | … | |
fetch-exists |
fetch remains the primary surface that triggers an LNA prompt for cross-address-space requests. | typeof | … | |
permissions-query-callable |
navigator.permissions.query exists so userland can probe the local-network and loopback-network permissions. | script | … | |
xhr-still-exists |
XMLHttpRequest is still exposed; LNA gates the underlying request but does not remove the API. | exists | … | |
permissions-policy-introspection |
Permissions Policy is the surface the LocalNetworkAccessPermissionsPolicyDefaultEnabled enterprise policy plumbs through; an allowsFeature surface exists. | script | … | |
private-network-access-superseded |
The old PNA preflight required a `Access-Control-Request-Private-Network` header; userland can still construct that header even though it is no longer the gating mechanism. | script | … |