← back to v151 · permission-policy-merger-direct-sockets-private-with-local-network-and-loopback-
conformance · v151
v151 · permission-policy-merger-direct-sockets-private-with-local-network-and-loopback- — 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 |
|---|---|---|---|---|
iframe-allow-attribute |
HTMLIFrameElement exposes an `allow` attribute — the surface that carries new local-network and loopback-network permissions-policy directives. | script | … | |
tcpsocket-only-in-isolated-context |
TCPSocket is gated by [SecureContext, IsolatedContext]; in a regular page the constructor must NOT be present on the global. Asserting absence avoids accidentally green-lighting a leaked surface. spec ↗ | script | … | |
direct-sockets-private-removed |
The merged feature replaces the old 'direct-sockets-private' policy. If the page exposes permissionsPolicy.features(), the legacy name should no longer be advertised. spec ↗ | script | … | |
local-network-policy-known |
If permissionsPolicy.features() is available, it should advertise 'local-network' as a known directive name. spec ↗ | script | … | |
loopback-network-policy-known |
Similarly 'loopback-network' should appear among advertised features when the introspection surface is present. spec ↗ | script | … | |
tcpsocket-construction-throws-without-policy |
In a normal browsing context (non-IWA), attempting to construct TCPSocket must throw — either because the constructor is undefined or because policy denies it. spec ↗ | throws | … |