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

visibilityState no longer works with concurrency>1 after chrome 120 #2808

Open
frankborden opened this issue Sep 18, 2024 · 0 comments
Open

Comments

@frankborden
Copy link

We have some code that uses visibilityState for reporting etc.
When we upgraded our tests from Chrome 120 to 128/129, they started to fail and timeout, showing visibilityState surprisingly becomes "hidden" and likewise our focus/blur event get stopped causing additional failures.
We found that forcing serial tests fixed this issue, but of course we would prefer to keep the concurrency for speed.

I made a simple reproduction with code like this in a click handler:

if (document.visibilityState === "visible") {
  this.count++;
}

and some tests that click the button and assert the count increase. The tests only pass with concurrency=1, but it used to work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant