On 2/10/26 3:45 p.m., Hubert Chao wrote:

Done. Apologies, wasn't sure if this needed to be done for this change.
Thanks Hubert.

On Tuesday, February 10, 2026 at 3:30:58 PM UTC-5 Mike Taylor wrote:

    Can you please request the various review bits in your
    chromestatus entry (i.e., privacy, security, enterprise...)?

    On 2/10/26 1:52 p.m., Chromestatus wrote:
    *Contact emails*
    [email protected]

    *Explainer*
    /No information provided/

    *Specification*
    /No information provided/

    *Summary*
    Local Network Access (LNA) restrictions have been recently added
    in the last few months to restrict web sites from unilaterally
    making requests to local networks and local devices
    (https://chromestatus.com/feature/5152728072060928
    <https://chromestatus.com/feature/5152728072060928>). This was
    added for Service Worker-initiated fetch requests, but was not
    done for navigations done by service workers through
    WindowClient.navigate This launch closes this hole by adding LNA
    restrictions to WindowClient.navigate() calls, using the
    WindowClient as the initiator of the navigation to determine if
    the navigation is an LNA request. This only applies if the
    WindowClient being navigated is a subframe; Chrome does not
    currently enforce any LNA restrictions on main frame navigations.

    *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*
    /No information provided/

    *Initial public proposal*
    /No information provided/

    *TAG review*
    /No information provided/

    *TAG review status*
    Pending

    *Risks*


    *Interoperability and Compatibility*
    /No information provided/

    /Gecko/: No signal

    /WebKit/: No signal

Do we not have any official signals for LNA generally? I looked at https://chromestatus.com/feature/5152728072060928 and see an I2P for Mozilla, but nothing for WebKit. Can we file something if not?

Also, can we update this chromestatus entry with both, once we have them?


    /Web developers/: No signals

    /Other signals/:

    *WebView application risks*

    Does this intent deprecate or change behavior of existing APIs,
    such that it has potentially high risk for Android WebView-based
    applications?

    /No information provided/


    *Debuggability*
    /No information provided/

    *Will this feature be supported on all six Blink platforms
    (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?*
    No

    *Is this feature fully tested by web-platform-tests
    
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?*
    No

Why not?



    *Flag name on about://flags*
    /No information provided/

    *Finch feature name*
    /No information provided/

    *Non-finch justification*
    /No information provided/

    *Rollout plan*
    Will ship enabled for all users

    *Requires code in //chrome?*
    False

    *Estimated milestones*
    Shipping on desktop         147
    Shipping on Android         147



    *Anticipated spec changes*

    Open questions about a feature may be a source of future web
    compat or interop issues. Please list open issues (e.g. links to
    known github issues in the project for the feature specification)
    whose resolution may introduce web compat/interop risk (e.g.,
    changing to naming or structure of the API in a
    non-backward-compatible way).

    The service worker spec dealing with the navigate() call will
    need to be modified to take into account the LNA checks
    (specifically, here
    https://www.w3.org/TR/service-workers/#client-navigate
    <https://www.w3.org/TR/service-workers/#client-navigate>)

    *Link to entry on the Chrome Platform Status*
    https://chromestatus.com/feature/5172375182245888?gate=6499217281515520
    <https://chromestatus.com/feature/5172375182245888?gate=6499217281515520>

    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]
    <mailto:[email protected]>.
    To view this discussion visit
    
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/698b7e59.050a0220.29f6fd.0634.GAE%40google.com
    
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/698b7e59.050a0220.29f6fd.0634.GAE%40google.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/a299d8ce-3ee8-40e5-bdc7-fe101f622287%40chromium.org.

Reply via email to