On Wed, Feb 11, 2026 at 10:03 AM Hubert Chao <[email protected]> wrote:

> On Tuesday, February 10, 2026 at 8:42:40 PM UTC-5 [email protected]
>  wrote:
>
> Is any spec update (https://wicg.github.io/local-network-access) needed
> to reflect this change or is this behavior implied by what's already there?
>
>
> I added a quick update to it just now (meant to do it yesterday but got
> sidetracked).  See
> https://wicg.github.io/local-network-access/#issue-f5cf3665
>

Normally our bar for spec work is that an algorithm is described precisely
somewhere, whether in the official spec, a monkey patch spec like this or a
PR. Normally an open issue would not be considered sufficient for an
I2S. With firefox now implementing, I assume there'd be support for getting
spec changes landed in the HTML spec, is that right? To what extent are you
/ your team actively engaged in driving the upstream spec work for LNA?

On Wed, Feb 18, 2026 at 5:54 AM Yoav Weiss (@Shopify) <
[email protected]> wrote:

>
> On Tuesday, February 10, 2026 at 11:08:17 PM UTC+1 Hubert Chao wrote:
>
> On Tue, Feb 10, 2026 at 4:16 PM Mike Taylor <[email protected]>
> wrote:
>
>
>
> *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?
>
> Firefox is shipping their LNA implementation, first to their users
> with Enhanced Tracking Protection on.
>
> https://support.mozilla.org/en-US/kb/control-personal-
> device-local-network-permissions-firefox
>
> We have heard nothing from webkit. We did a request for position with the
> first LNA launch
>
> https://github.com/WebKit/standards-positions/issues/520
>
> and annevk has posted some on the github spec repo about the permission
> names (https://github.com/WICG/local-network-access/issues/17), but we
> haven't heard anything else from them. Is this something where we should
> proactively ping 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
>
>
> For this specific fix, we tested with browser tests.
>
> In general for LNA, we have some basic WPT's checked in (
> https://source.chromium.org/chromium/chromium/src/+/main:
> third_party/blink/web_tests/external/wpt/fetch/local-network-access/),
> but we don't have everything tested in WPT that we do in chromium browser
> tests. Its something we've been meaning to do but haven't gotten around to
> due to other competing priorities around LNA (most notably the split
> permissions).
>
>
> Not having WPTs for this increases the interoperability risk (e.g.
> Increases the probability that Firefox folks forget about this particular
> part).
> Can you bump up the priority of adding these WPTs?
>

+1, now that Firefox is shipping WPTs are really essential (or we should
assume there will be interop issues).

I suspect that our robot overlords are likely to do a good job
> "translating" the browser tests to WPTs..
>
>
>
> /hubert
>
> --
> 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/5040db20-92b4-4c15-bb72-485f163903f8n%40chromium.org
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5040db20-92b4-4c15-bb72-485f163903f8n%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/CAFUtAY-ik9Yw%2BpUoicratqb-COS4V_dZv%2Bo%3D4hfi-yq4kTNFKQ%40mail.gmail.com.

Reply via email to