LGTM3, also contingent on all the other approvals (per Rick's note). Best,
Alex On Wednesday, October 7, 2026 at 9:03:22 AM UTC-7 Hubert Chao wrote: > 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 > <https://github.com/WICG/local-network-access/commit/345eafde94fe9a3f81d29f6bed6d055643cd4717>, > > then removed Jul 6, 2026 here > <https://github.com/WICG/local-network-access/commit/92657b3869920d973aea00c93e861c4b8751bda9> > ). > > It was in the PNA spec (here > <https://wicg.github.io/private-network-access/#csp>); 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 > > > On Wed, Oct 7, 2026 at 11:32 AM Rick Byers <[email protected]> wrote: > >> 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 >> >> On Wed, Oct 7, 2026 at 5:27 PM Rick Byers <[email protected]> wrote: >> >>> It looks like this was removed from the spec here >>> <https://github.com/WICG/local-network-access/commit/314cb7ad46d6c10a9498551a445a7cd7f3cfbc0c>, >>> >>> 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 >>> >>> On Wed, Oct 7, 2026 at 5:20 PM Chris Harrelson <[email protected]> >>> wrote: >>> >>>> LGTM1 >>>> >>>> On Wed, Sep 30, 2026 at 12:25 PM Hubert Chao <[email protected]> >>>> wrote: >>>> >>>>> One thing that may not be clear: the plan here is to remove the header >>>>> directly without a deprecation trial. >>>>> On Wednesday, September 30, 2026 at 3:22:59 PM UTC-4 Chromestatus >>>>> wrote: >>>>> >>>>>> *Contact emails* >>>>>> [email protected] >>>>>> >>>>>> *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 >>>>>> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%20%3E%20SecurityFeature%20%3E%20LocalNetworkAccess%22> >>>>>> >>>>>> *Web Feature ID* >>>>>> local-network-access >>>>>> <https://webstatus.dev/features/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 >>>>>> <https://chromestatus.com>. >>>>>> >>>>> -- >>>>> 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 [email protected]. >>>>> To view this discussion visit >>>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/80795d4e-33ef-4636-a047-c3d289026300n%40chromium.org >>>>> >>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/80795d4e-33ef-4636-a047-c3d289026300n%40chromium.org?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- >>>> 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 [email protected]. >>>> To view this discussion visit >>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_a76_7KM6HyPbs%3DkLyWiLZ7bK%2BUUv6GjVJdgFUqCFvGw%40mail.gmail.com >>>> >>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_a76_7KM6HyPbs%3DkLyWiLZ7bK%2BUUv6GjVJdgFUqCFvGw%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- 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 [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/669e3366-272f-4560-81f7-bcb4586fcfc8n%40chromium.org.
