v151 · Permissions Policy · Direct Sockets

Policy Inheritance Explorer

Permissions Policy propagates through nested iframes via inheritance — a parent can only delegate permissions it already has. This explorer shows how the merged direct-sockets-private / local-network / loopback-network directive flows through a three-level frame tree. Set each frame's allow attribute and see which permissions survive to the leaf.

Frame configuration
Top-level page (HTTP header)
Child iframe allow=""
Grandchild iframe allow=""
Frame
direct-sockets-private
local-network (merged)
loopback-network (merged)
The merge rule

Chrome 151 merges the three directives: any policy on direct-sockets-private also applies to local-network and loopback-network when accessing private addresses via Direct Sockets.

Previously these were three independent directives you had to list separately. After the merge, setting Permissions-Policy: direct-sockets-private=() automatically restricts local-network and loopback-network for the same context.

see also

implementation reference

Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗