[Bug]: WDIO cannot communicate with Electron because of BrowserWindow did not seem to return anything to WDIO if you don't call LoadURL

[angeljudgement]

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a bug report that matches the one I want to file, without success.

Electron Version

26.0.0+

What operating system are you using?

Windows

Operating System Version

22H2

What arch are you using?

x64

Last Known Working Electron version

25.9.1

Expected Behavior

forcing a response to WDIO.remote method without involving BrowserWindow.loadUrl

Actual Behavior

#40268
As this issue here isn't seem to be solved. I found the root cause of all this deed is due to BrowserWIndow did not return response to WDIO Remote method, this leads to timeout and forcing to close.
A good approach to fix this problem is to use BrowserWIndow.loadURL(about:blank) directly (not loading URL from webcontent). But this will cause focus issue, if you focus on BrowserWindow with 2 or 3 webcontents, the focus will be trigger thrice

Testcase Gist URL

No response

Additional Information

No response

[electron-issue-triage]

Hello @angeljudgement. Thanks for reporting this and helping to make Electron better!

Would it be possible for you to make a standalone testcase with only the code necessary to reproduce the issue? For example, Electron Fiddle is a great tool for making small test cases and makes it easy to publish your test case to a gist that Electron maintainers can use.

Stand-alone test cases make fixing issues go more smoothly: it ensure everyone's looking at the same issue, it removes all unnecessary variables from the equation, and it can also provide the basis for automated regression tests.

Now adding the blocked/need-repro Needs a test case to reproduce the bug label for this reason. After you make a test case, please link to it in a followup comment. This issue will be closed in 10 days if the above is not addressed.

[electron-issue-triage]

Unfortunately, without a way to reproduce this issue, we're unable to continue investigation. This issue has been closed and will not be monitored further. If you're able to provide a minimal test case that reproduces this issue on a supported version of Electron please open a new issue and include instructions for reproducing the issue.