Intent to Deprecate and Remove: RemoveTreatAsPublicAddress

247 views
Skip to first unread message

Chromestatus

unread,
Sep 30, 2026, 3:22:59 PMSep 30
to blin...@chromium.org, jdeb...@chromium.org, cth...@chromium.org, hc...@chromium.org
Contact emails
hc...@chromium.org

Explainer
No information provided

Specification
No information provided

Summary
The Content Security Policy header treat-as-public-address was added as part of Private Network Access to allow non-documents to declare themselves as being in the public address space (https://wicg.github.io/private-network-access/#csp). It is primarily useful for testing. https://github.com/WICG/private-network-access/issues/88 highlights some issues with this header, and the decision was made to remove this header instead of moving it somewhere else. For testing use cases, the --ip-address-space-overrides command line flag can be used. This header was only ever implemented in Chromium; Firefox has never implemented this header and has no plans to. Safari has not implemented Private Network Access or Local Network Access and so does not have the header either.

Blink component
Blink > SecurityFeature > LocalNetworkAccess

Web Feature ID
local-network-access

Motivation
Header does not fit well into Content Security Policy, and it was deemed unnecessary given the alternative of using `--ip-address-space-overrides` Metrics show this is barely used: https://chromestatus.com/metrics/feature/timeline/popularity/5983

Initial public proposal
No information provided

Goals for experimentation
None

Debuggability
No information provided

Requires code in //chrome?
False

Tracking bug
https://issues.chromium.org/issues/527730705

Estimated milestones

No milestones specified



Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5187021965492224?gate=5964820426915840

This intent message was generated by Chrome Platform Status.

Hubert Chao

unread,
Sep 30, 2026, 3:25:52 PMSep 30
to blink-dev, Chromestatus, Joe DeBlasio, Chris Thompson, Hubert Chao
One thing that may not be clear: the plan here is to remove the header directly without a deprecation trial.

Chris Harrelson

unread,
Oct 7, 2026, 11:20:29 AMOct 7
to Hubert Chao, blink-dev, Chromestatus, Joe DeBlasio, Chris Thompson
LGTM1

--
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/80795d4e-33ef-4636-a047-c3d289026300n%40chromium.org.

Rick Byers

unread,
Oct 7, 2026, 11:27:55 AMOct 7
to Chris Harrelson, Hubert Chao, blink-dev, Chromestatus, Joe DeBlasio, Chris Thompson
It looks like this was removed from the spec here, so I've added that as the spec link.

Please request the additional reviews required for deprecation and removal (we upgraded the chromestatus entry from just 'plan' to a full removal since it appears that's what you're asking for).

I assume this will have a killswitch, just in case some enterprise was somehow relying on it or something, right?

LGTM2 conditional on the above.

Rick

Rick Byers

unread,
Oct 7, 2026, 11:33:06 AMOct 7
to Chris Harrelson, Hubert Chao, blink-dev, Chromestatus, Joe DeBlasio, Chris Thompson
Actually sorry, it looks like we aren't able to correct the stage for you in the tool. Please set the stage to "prepare to ship", the tool will require you to get (for example) Enterprise approval for shipping a breaking change.

Rick

Hubert Chao

unread,
Oct 7, 2026, 12:03:22 PMOct 7
to Rick Byers, Chris Harrelson, blink-dev, Chromestatus, Joe DeBlasio, Chris Thompson
Set the stage; requested all of the prepare to ship approvals. I'll post here when I have all of the approvals.

Forgot this was added to the LNA spec, I will note that it was in the LNA spec for less than 3 weeks (added Jun 15, 2026 here, then removed Jul 6, 2026 here).

It was in the PNA spec (here); the LNA spec copied the PNA text for the three-week period when we thought we would keep it, before deciding to remove it entirely.

/hubert
 

Alex Russell

unread,
Oct 12, 2026, 2:45:58 PM (9 days ago) Oct 12
to blink-dev, Hubert Chao, Chris Harrelson, blink-dev, Chromestatus, Joe DeBlasio, Chris Thompson, Rick Byers
LGTM3, also contingent on all the other approvals (per Rick's note).

Best,

Alex

LGTM1

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

--
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+unsubscribe@chromium.org.

Philip Jägenstedt

unread,
Oct 14, 2026, 11:19:57 AM (8 days ago) Oct 14
to Alex Russell, blink-dev, Hubert Chao, Chris Harrelson, Chromestatus, Joe DeBlasio, Chris Thompson, Rick Byers
LGTM4 (to reflect my approval in the tool to get that to 3xLGTM)

LGTM1

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

--
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.

--
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/669e3366-272f-4560-81f7-bcb4586fcfc8n%40chromium.org.

Hubert Chao

unread,
Oct 15, 2026, 12:41:31 PM (7 days ago) Oct 15
to Philip Jägenstedt, Alex Russell, blink-dev, Chris Harrelson, Chromestatus, Joe DeBlasio, Chris Thompson, Rick Byers
FYI all prepare to ship approvals have been obtained.

Going ahead w/ removal, thanks all!
Reply all
Reply to author
Forward
0 new messages