← back to v145 · local-network-access-split-permissions
conformance · v145
v145 · local-network-access-split-permissions — 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 |
|---|---|---|---|---|
permissions-api-exists |
navigator.permissions is the surface where the new split permissions (local-network, loopback) are queried. | exists | … | |
permissions-query-is-function |
navigator.permissions.query is a function — used to query each of the new permission names. | typeof | … | |
permissions-query-local-network |
navigator.permissions.query({name:'local-network'}) does not reject — the new permission name is recognised. spec ↗ | script | … | |
permissions-query-loopback |
navigator.permissions.query({name:'loopback'}) is feature-detectable, returning a PermissionStatus or a clean unsupported-name TypeError. spec ↗ | script | … | |
fetch-still-exists |
fetch is the surface gated by the split permissions; same API, finer-grained gating. | typeof | … |