PSA: Changes to the fetch() option `targetAddressSpace`

75 views

Skip to first unread message

Chris Thompson

unread,

May 20, 2025, 7:00:57 PMMay 20

to blink-dev

Hello blink-dev@ --

As part of our work on Local Network Access restrictions (which is superseding a prior effort called Private Network Access), we will be making some changes to the fetch option targetAddressSpace. While this option technically shipped as part of work on the Private Network Access mixed content permission, it was never meaningfully web-exposed as Private Network Access' enforcement has not shipped (only DevTools warnings). Sites that adopted this optional tagging of fetch() calls should not be affected by this change.

Specifically, we are moving this fetch() option from being gated on the "PrivateNetworkAccessPermissionPrompt" runtime enabled feature to being gated on the new "LocalNetworkAccessPermissionPolicy" runtime enabled feature (which is controlled by the base::Feature flag "LocalNetworkAccessChecks"). As part of this change, we will also be updating the values for the targetAddressSpace option to match the new address space names, as described in our explainer. These changes will ship in Chrome 138.

The new Local Network Access feature will be ready for developer testing soon, and we will share more details in a separate announcement.

Mike Taylor

unread,

May 21, 2025, 8:40:40 AMMay 21

to Chris Thompson, blink-dev

Thanks for sending the PSA, Chris.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALMy46QojdKYkYj438Kexy9axkDxPQsY4vrQ2Uy%3DYpHrqXi55Q%40mail.gmail.com.

Reply all

Reply to author

Forward

0 new messages