Handle Chrome's Local Network Access permission prompt

[sam-yh]

What is your Scenario?

Summary

Chrome introduced a "Local Network Access permission prompt" in Chrome 141.
According to https://developer.chrome.com/blog/local-network-access this is planned for Chrome 142, but I'm seeing it right now in both Linux and Windows builds of Chrome 141.

This prompt looks like this:

and blocks TestCafe tests from running until the prompt is handled. Also affects headless mode.

It would be good to have a flag or similar to auto-handle it.

I'm aware that this might not be something TestCafe can solve, but just in case, I wanted to file a request.

To observe the issue:

Just run testcafe chrome with Chrome 141 against a file like this:

fixture`Chrome141`.page`${'https://testcafe.io'}`

test('Chrome141', async t => {
    await t.wait(1000)
})

What are you suggesting?

It may depend on Chrome providing a way to disable or auto-handle the chrome://flags/#local-network-access-check flag.
I don't know if there is some way Testcafe devs can provide a workaround or other way to deal with the flag / the prompt.

What alternatives have you considered?

Tried await t.setNativeDialogHandler() which doesn't work.
Looked for a cli flag for chrome, couldn't find one.

Additional context

I apologize if this doesn't fit the feature request format.

[sam-yh]

A workaround that depends on disabling native automation, that has worked for me:

testcafe --disable-native-automation chrome --disable-features=LocalNetworkAccessCheck  path/to/file

[lloydwatkin]

This fixed CI runs for us, thanks!

On ubuntu (ARM64) and locally (M2 Pro Mac - not sure if the processor is relevant)

testcafe --disable-native-automation chrome:headless --disable-features=LocalNetworkAccessCheck ./tests

[gforepsly]

We have the same issue, starting from this morning. Disabling native automation is not advised as far as we know, so this is not a good workaround.
Is there another way to handle it? This is a real blockage at the moment.

EDIT:
The above solutions does NOT work on MAC M1 PRO, the prompt keeps on popping.

[TrinuxSG]

Using these chrome flags didn't work:

const CHROME_FLAGS = '--disable-features=PrivateNetworkAccessCheck';
const CHROME_FLAGS = '--enable-features=PrivateNetworkAccessNonSecureContextsAllowed';
const CHROME_FLAGS = '--disable-features=PermissionsPromptOnLocalNetworkAccess';

Downgrading to previous 140 version seems a temporary solution

[dhruvfarswan]

This worked for us -
"browsers": "chrome --disable-features=LocalNetworkAccessChecks"

[gforepsly]

This worked for us - "browsers": "chrome --disable-features=LocalNetworkAccessChecks"

Doesn't work on our side. Nothing above is working (neither on Linux machines, nor MAC M1 Pro).
We will try to downgrade Chrome, as we are 100% blocked with this beautiful new feature from google.

EDIT:
Edge works also, without any issues.

[louisnelza]

Sucks! Using Edge or Firefox.

[github-actions]

We appreciate you taking the time to share information about this issue. We reproduced the bug and added this ticket to our internal task queue. We'll update this thread once we have news.