chore: allow local-network-access permission in chromium#37871
chore: allow local-network-access permission in chromium#37871yury-s merged 2 commits intomicrosoft:mainfrom
Conversation
|
Not sure if we want to support this, given that "permission prompt for Local Network Access" is still an [opt-in experiment]( permission prompt for Local Network Access) in Chrome. |
dgozman
left a comment
There was a problem hiding this comment.
I think this one is good. It looks like LNA is going to be enabled by default in 142 (https://chromestatus.com/feature/5152728072060928), so unblocking this usecase is nice. I am afraid that we'll have to disable it if too many customers are affected in the next release.
Can we add a test, or is that too hard given the IP shenanigans?
|
Thank you for the quick turnaround on this!
I commented about this here: #37861 (comment) My gut feeling is that most people won't be affected by this because they will likely fall into "all private" or "all public" buckets of access patterns. We were affected because our desire for consistent infrastructure between dev/staging/prod meant putting the root URL behind CF (technically making it public) while other services were kept private. But it will be nice to have an escape hatch for those of us in the unconventional "public -> private" bucket. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
c89ece1 to
f02fa79
Compare
Test results for "MCP"2570 passed, 108 skipped Merge workflow run. |
Test results for "tests 1"2 failed 2 flaky47095 passed, 815 skipped Merge workflow run. |
Feature status: https://chromestatus.com/feature/5152728072060928 Looks like it got enabled between 1.56.0-alpha-2025-09-12 and 1.56.0-alpha-2025-09-11 which correspond to Chromium 141.0.7390.16 and 141.0.7390.7.
Blink thread: https://groups.google.com/a/chromium.org/g/blink-dev/c/cwu_RUmBpzY?utm_source=chatgpt.com&pli=1
Fixes #37861