Hello blink-dev@ --

As part of our work on Local Network Access restrictions
<https://chromestatus.com/feature/5152728072060928> (which is superseding a
prior effort called Private Network Access
<https://chromestatus.com/feature/5737414355058688>), 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 <https://chromestatus.com/feature/5954091755241472>, 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
<https://github.com/explainers-by-googlers/local-network-access/blob/main/README.md#address-spaces>.
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.

-- 
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+unsubscr...@chromium.org.
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALMy46QojdKYkYj438Kexy9axkDxPQsY4vrQ2Uy%3DYpHrqXi55Q%40mail.gmail.com.

Reply via email to