updated feature: Permission Policy Merger: "direct-sockets-private" with "local-network" and "loopback-network"

Skip to first unread message

Chromestatus

unread,
May 11, 2026, 6:18:43 AM (11 days ago) May 11
to iwa...@chromium.org
Chrome Platform Status
 Updated feature entry:
Permission Policy Merger: "direct-sockets-private" with "local-network" and "loopback-network"
Updates made by bhaska...@google.com:
  • accurate_as_of:
    Old: 2026-04-09 15:37:50.288577
    New: 2026-05-11 10:17:34.378367

Your next steps:

You are receiving this email because:

  • You are subscribed to all IWA features

Unsubscribe

Chromestatus

unread,
May 13, 2026, 6:47:48 AM (9 days ago) May 13
to iwa...@chromium.org
Chrome Platform Status
Updates made by bhaska...@google.com:
  • summary:
    Old: Isolated Web App manifests now require specific "local-network" or "loopback-network" permission policies, in addition to "direct-sockets-private", to enable Direct Sockets connections to local or loopback network addresses, respectively. This provides developers with more granular control over network access and enhances application security by making network requirements more transparent within the manifest. To avoid breaking existing Isolated Web Apps, there's a temporary compatibility measure in place. Until Chrome 151, "direct-sockets-private" will automatically unpack to "local-network" and "loopback-network" respectively.
    New: Isolated Web App manifests now require specific "local-network" and/or "loopback-network" permission policies to enable Direct Sockets connections to local or loopback network addresses, respectively. This change replaces the existing "direct-sockets-private" permission policy. This provides developers with more granular control over network access and enhances application security by making network requirements more transparent within the manifest. To avoid breaking existing Isolated Web Apps, there's a temporary compatibility measure in place. Until Chrome 151, "direct-sockets-private" will automatically unpack to "local-network" and "loopback-network" respectively.

  • accurate_as_of:
    Old: 2026-05-11 10:17:34.378367
    New: 2026-05-13 10:46:38.588606

Your next steps:

Chromestatus

unread,
May 13, 2026, 6:52:04 AM (9 days ago) May 13
to iwa...@chromium.org
Chrome Platform Status
Updates made by bhaska...@google.com:
  • summary:
    Old: Isolated Web App manifests now require specific "local-network" and/or "loopback-network" permission policies to enable Direct Sockets connections to local or loopback network addresses, respectively. This change replaces the existing "direct-sockets-private" permission policy. This provides developers with more granular control over network access and enhances application security by making network requirements more transparent within the manifest. To avoid breaking existing Isolated Web Apps, there's a temporary compatibility measure in place. Until Chrome 151, "direct-sockets-private" will automatically unpack to "local-network" and "loopback-network" respectively.

  • New: Isolated Web App manifests now require specific "local-network" and/or "loopback-network" permission policies to enable Direct Sockets connections to local or loopback network addresses, respectively. This change replaces the existing "direct-sockets-private" permission policy. This provides developers with more granular control over network access and enhances application security by making network requirements more transparent within the manifest.

  • accurate_as_of:
    Old: 2026-05-13 10:46:38.588606
    New: 2026-05-13 10:51:52.370808

Your next steps:

Chromestatus

unread,
May 13, 2026, 8:43:26 AM (9 days ago) May 13
to iwa...@chromium.org
Chrome Platform Status
Updates made by vk...@google.com:
  • accurate_as_of:
    Old: 2026-05-13 10:51:52.370808
    New: 2026-05-13 12:42:18.259935

Your next steps:
Reply all
Reply to author
Forward
0 new messages