Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chrome's search engine prompt causes testcafe process to fail #8241

Closed
maksnester opened this issue Jul 25, 2024 · 2 comments
Closed

Chrome's search engine prompt causes testcafe process to fail #8241

maksnester opened this issue Jul 25, 2024 · 2 comments
Labels
STATE: Duplicate An issues has been already reported in the other thread. TYPE: bug The described behavior is considered as wrong (bug).

Comments

@maksnester
Copy link

What is your Scenario?

See this article explaining the prompt https://www.ghacks.net/2023/12/09/google-chrome-to-display-choose-your-search-engine-prompt/

Error: Unable to open the "chrome:" browser due to the following error:

Error: WebSocket connection closed
    at /Users/me/projects/org-accountsettings-client/node_modules/chrome-remote-interface/lib/chrome.js:94:35
    at Chrome._handleConnectionClose (/Users/me/projects/org-accountsettings-client/node_modules/chrome-remote-interface/lib/chrome.js:256:13)
    at WebSocket.<anonymous> (/Users/me/projects/org-accountsettings-client/node_modules/chrome-remote-interface/lib/chrome.js:243:22)
    at WebSocket.emit (node:events:517:28)
    at WebSocket.emit (node:domain:489:12)
    at WebSocket.emitClose (/Users/me/projects/org-accountsettings-client/node_modules/chrome-remote-interface/node_modules/ws/lib/websocket.js:246:10)
    at Socket.socketOnClose (/Users/me/projects/org-accountsettings-client/node_modules/chrome-remote-interface/node_modules/ws/lib/websocket.js:1148:15)
    at Socket.emit (node:events:517:28)
    at Socket.emit (node:domain:489:12)
    at TCP.<anonymous> (node:net:350:12)
    at TCP.callbackTrampoline (node:internal/async_hooks:130:17)
    at BrowserConnection._runBrowse

What is the Current behavior?

When I run testcafe I see chrome opens briefly with that prompt and then testcafe fails and kills the browser before I can select anything there to make that prompt to go away.

What is the Expected behavior?

Let the browser to hang a little or suggest some chrome flag that can forbid this prompt if there is any.

What is the public URL of the test page? (attach your complete example)

yeah right

What is your TestCafe test code?

doesn't matter here

Your complete configuration file

"browsers": ["chrome --window-size=1280,800 --no-sandbox --disable-dev-shm-usage"],
disableNativeAutomation": false

The last one is important as it happens only in that case. When it is disabled, I have time to select the search engine in prompt and test continues. But when I run tests the next time I see the prompt again, so my selection is not saved for some reason.

Your complete test report

No response

Screenshots

No response

Steps to Reproduce

I don't know the exact steps to cause chrome to show this dummy modal window.

TestCafe version

3.6.2

Node.js version

v18.18.0

Command-line arguments

irrelevant, I use createTestCafe and didn't change any args

Browser name(s) and version(s)

Version 127.0.6533.73 (Official Build) (arm64)

Platform(s) and version(s)

macOS 14.5 (23F79)

Other

My settings in chrome are not saved, even if I manually open chrome/flags and turn off that search engine dialog, on the next run I see it again.

@maksnester maksnester added the TYPE: bug The described behavior is considered as wrong (bug). label Jul 25, 2024
@testcafe-need-response-bot testcafe-need-response-bot bot added the STATE: Need response An issue that requires a response or attention from the team. label Jul 25, 2024
@vasilyevi
Copy link

vasilyevi commented Jul 26, 2024

same to me total blocker
workaround: --disable-search-engine-choice-screen

@PavelMor25
Copy link
Collaborator

Hello @maksnester,

Thank you for your report.

Please refer to the #8240 issue. I'll close this issue as a duplicate.

@PavelMor25 PavelMor25 closed this as not planned Won't fix, can't repro, duplicate, stale Jul 29, 2024
@testcafe-need-response-bot testcafe-need-response-bot bot removed the STATE: Need response An issue that requires a response or attention from the team. label Jul 29, 2024
@PavelMor25 PavelMor25 added the STATE: Duplicate An issues has been already reported in the other thread. label Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
STATE: Duplicate An issues has been already reported in the other thread. TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

3 participants