Cypress v13.6.0 no longer running commands (hangs) when we focus out of the window

[Julien-Marcou]

Current behavior

When I launch my E2E tests on Chrome, if I focus out of the Chrome window, the E2E commands are no longer running, it's hanging there doing nothing.

If I always stay focused on the Chrome window, the commands work as expected.

After focusing out, re-focusing in the window does not make the commands continue/restart.

Might be related to this PR this #28334

Desired behavior

I should be able to run E2E tests while not being focused on Chrome (as before) so I can do something else while the E2E tests are running.

Test code to reproduce

Sorry I don't have time to create a reproduction of the bug for the moment

Cypress Version

13.6.0

Node version

v18.18.2

Operating System

macOS 14.1.1

Debug Logs

No response

Other

No response

[jennifer-shehane]

@Julien-Marcou That's certainly not intended. We haven't observed this behavior so I wonder if it is something specific with your tests. A reproducible example or a video of the hanging behavior would be helpful. We'll keep an eye on tracking for this.

[esetnik]

I am experiencing the same issue in v13.6.0

[stephenmday]

I am experiencing this issue as well in 13.6.0 When I open a test in test runner it runs correctly, but if I go to VS Code and make a change to the code and save, normally the test will run again in test runner, but it hangs. I have to stop and restart the test every time I make a change to the code.

[EllenFr]

I have the same focus issue with Cypress 13.6.0 and Chrome 119 but it does not occur when selecting Edge, Firefox or Electron. In my case, saving changes in VS Code still causes the test runner to start over but because the focus was lost, the process stops there.

[valantic-dev]

We are experiencing the same issue after we updated to v13.6.0
The tests are executed in an Azure Pipeline and stop sending out the requests after 2-3 hours of execution.
Additionally, the issue @stephenmday and @EllenFr described appears on my local machine, too.
We went back to v13.5.1 for now.

NOTE:
I think I should mention that we are sending an HTTP request in "beforeAll" hook of each test to ensure that the test environment is initialized correctly. This one specific request is the one that gets stuck.

It's a globally defined "beforeAll" hook in the e2e.ts

[alexsch01]

I see the same issue with 13.6.0

[chrisbreiding]

Does anyone have a clone-able repo that can be used to reliably reproduce this issue? I've tried a few projects, but can't recreate the described behavior, so I wonder if there's something project-specific that I'm missing. A way to reproduce it locally would provide a way forward to diagnose and fix the problem.

[elebitzero]

I am seeing this constantly when running Cypress 13.6.0 with latest Chrome interactively on Windows.

If the Cypress window loses focus it will hang.

Even if I let it run, it eventually hangs when it gets to some download tests because the browser pops up a tooltip: 'Find your downloads here'.

[iomedico-beyer]

Steps to reproduce:

1. Run in "open" mode with Chrome, Edge or Electron.

cy.get("#some-text-field").type("foo-bar-baz", { delay: 1000 }).blur()

2. Wait until Cypress starts typing.
3. Before blur you have plenty of time (about 10 seconds) to click on another window.
4. Defocusing of the window leads to defocussing of the text field, so type kind of freezes and blur fails:

cy.blur() can only be called when there is a currently focused element.

Note that in Firefox the text field does not loose focus unwantedly until the Firefox window gets the focus back.

[jennifer-shehane]

@iomedico-beyer I'm not able to reproduce this behavior from this example still :/

We are looking into the possibility that this issue may be the cause: #28443

If you open devTools after the hang, do you see a message like below?

Uncaught Error: Attempting to use a disconnected port object

[valantic-dev]

cypress_136.zip

Hi @jennifer-shehane and @chrisbreiding , I created a video and captured the test execution incl. 2 scenarios when Cypress gets stuck.

1. During the test exeuction I open the browser console (via F12). As the console is openen, the execution stops and does not resume again. No errors like in Uncaught Error: Attempting to use a disconnected port object #28443 are in the console.
2. I restart the test execution and then switch to VSCode during the tests are running. Here again, the executions stops and does not resume.