Just like Chrome, Safari caps setInterval at 1000ms when the tab is inactive. requestAnimationFrame is always paused in inactive tabs. Starting from Edge 14, setInterval is capped at 1000ms in inactive tabs. It does not matter whether the window is out of focus or not. IE does not limit the delay in setInterval when the tab is inactive, but it pauses requestAnimationFrame in inactive tabs. #define DEFAULT_MIN_BACKGROUND_TIMEOUT_VALUE 1000 // 1000ms #define DEFAULT_MIN_TIMEOUT_VALUE 4 // 4ms The default shortest interval/timeout we permit However, requestAnimationFrame runs exponentially slower when the tab is inactive, with each frame taking 1s, 2s, 4s, 8s and so on. Similar to Chrome, Firefox limits the minimum interval of setInterval to around 1000ms when the tab (not the window) is inactive. Provides control over the minimum timer interval for background tabs.Ĭonst double kBackgroundTabTimerInterval = 1.0
requestAnimationFrame is paused when the tab is inactive. It does not matter if the window is out of focus, the interval is limited only when you switch to a different tab. If the interval is higher than 1000ms, it will run at the specified interval. You can see how frequently it is updated (or if it is ever updated) when you make the tab or window inactive.Ĭhrome limits the minimum interval of setInterval to around 1000ms when the tab is inactive. Test TwoĪnother way to test it is to log the timestamp repeatedly with setInterval and requestAnimationFrame and view it in a detached console. It will continue to log the actual time it takes for these functions in an inactive tab. To see what happens when you switch to a different tab or have an inactive window, simply open the page, switch to a different tab and wait for a while. requestAnimationFrame generally defaults to the 60fps depending on the browser. setTimeout works similarly to a setInterval with respect to delays. You can change the number of milliseconds for setInterval to see how it runs under different settings. The test logs the actual time it takes for a setInterval and requestAnimationFrame to run in different browsers, and gives you the results in the form of a distribution. requestAnimationFrame is not supported by IE 9- and Opera 12. I have written a test specifically for this purpose:įrame Rate Distribution: setInterval vs requestAnimationFrame
Do these changes happen if the window is out of focus, as opposed to just the tab? (I imagine it would be harder to detect, as it requires the OS API.).Which browsers reduce the setInterval repeat? Is it just reduced to a limit or by a percentage? For example, if I have a 10ms repeat versus a 5000ms repeat, how will each be affected?.Other than mobile browsers, do desktop browsers ever pause JS execution when a tab is not active? When and which browsers?.requestAnimationFrame is slowed when tab is not active (reasonable, can't think of why this would affect anyone too much).setInterval and setTimeout delay is reduced when tabs are not active - seems like this just started appearing recently and can mess up Jasmine unit tests, around other things.ios 5 pauses javascript when tab is not active.
#BE FOCUSED TIMER CHANGE TIME CODE#
Specifically, I would like to know how my Javascript code will be affected if the current tab is not active, or the browser window is not active, in different browsers. But, this question is not about the page visibility API. Background: I'm doing some user interface tests that need to detect if people are paying attention or not.
0 kommentar(er)
