Closed satbirkira closed 6 months ago
Hi @satbirkira
Thank you for pointing this out. We will investigate this behavior.
Bump
We have not investigated this yet. We will update this thread once we have any news.
Bump
No updates yet. Once we get any results, we will post them in this thread.
This issue has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this issue in the future. If it still affects you or you have any additional information regarding it, please leave a comment and we will keep it open.
We're closing this issue after a prolonged period of inactivity. If it still affects you, please add a comment to this issue with up-to-date information. Thank you.
There are two flags that we need to use to disable throttling if testcafe is not visible in the window: --disable-backgrounding-occluded-windows and --disable-background-timer-throttling
Neither of these flags will do anything if you pass them into chrome, unless you Temporarily unexpire M94 flags, and Temporarily unexpire M95 flags using chrome://flags/
The current solutions, even one merged in will not work.
Tests execution pauses when browser window is not visible #158
wentwrong:add-disable-backgrounding-flag
Even if you unexpire the chrome flags on your local chrome browser, the unexpire flag changes don't transfer into test cafe's chrome, because it uses a fresh chrome instance.
We need some way to boot chrome with M94 flags and M95 flags unexpired.
One workaround would have been making a test 0 which will go to chrome://flags/ and unexpire flags, but testcafe will complain that chrome://flags/ is not a supported protocol (like http/https/file).