bug, qq.com website encountered search error

[scoolor]

What is your Scenario?

qq.com Click search button, can not search

What is the Current behavior?

throw error window.reporter , object lost.

What is the Expected behavior?

There should be no errors and the website is working properly

What is your public website URL? (or attach your complete example)

https://www.qq.com

What is your TestCafe test code?

none

Your complete configuration file

none

Your complete test report

none

Screenshots

through proxy

without proxy

Steps to Reproduce

1. proxy site www.qq.com
2. input something, click on the search box at the top
3. not working

TestCafe version

latest

Node.js version

v20.10.0

Command-line arguments

chrome

Browser name(s) and version(s)

chrome 119

Platform(s) and version(s)

macos 13.1

Other

No response

[Bayheck]

Hello, I managed to reproduce your issue. However, could you please specify if you are using TestCafe or testcafe-hammerhead in your usage scenario?  In TestCafe, you can use a workaround. Set disableMultipleWindows to true in your configuration file or include the --disable-multiple-windows flag. This workaround works if you are using Native Automation (in TestCafe v3.0.0 and newer, native automation is the default setting). Furthermore, if you're using testcafe-hammerhead, please describe the specific purpose behind its usage in your case.

[scoolor]

Hello,

Thank you for your prompt response. I am using testcafe-hammerhead, specifically for testing proxy functionalities to ensure their reliability. My main focus is on validating the effectiveness of the proxy under various conditions and ensuring that it can handle the required tasks without any significant issues.

Thank you for your support!

[Bayheck]

Hello, TestCafe-Hammerhead is a proxy specifically designed to work with TestCafe. Using TestCafe-Hammerhead separately from TestCafe is not recommended.   The reported issue has a TestCafe workaround available when Native Automation is enabled. Due to this, the priority for addressing this issue is relatively low. As a result, we don’t currently have immediate plans to work on this task, and we'll close this issue.   However, if you'd like to contribute and have a solution in mind, feel free to create a pull request (PR) addressing this issue. We would appreciate any contributions and will gladly review any PRs submitted.   Thank you for your understanding and your interest in improving our platform.