When the window is minimized in chrome, time is ticking about 2 times slower, in the test-bed all norms are tested.
Closed due to the fact that it is necessary to reformulate the question so that it was possible to give an objectively correct answer by the participants of HamSter , iluxa1810 , Alex , post_zeew , user194374 26 Nov '16 at 9:49 .
The question gives rise to endless debates and discussions based not on knowledge, but on opinions. To get an answer, rephrase your question so that it can be given an unambiguously correct answer, or delete the question altogether. If the question can be reformulated according to the rules set out in the certificate , edit it .
|
1 answer
In some situations, the timer will operate less frequently than usual:
Most browsers (desktop first) continue to execute setTimeout / setInterval, even if the tab is inactive.
At the same time, a number of them (Chrome, FF, IE10) reduce the minimum frequency of the timer, to 1 time per second. It turns out that in the “background” tab the timer will work, but rarely.
lexxl lexxl
5,051 2 13 35
- I call the function once a second, and add "1" to it, that is, it turns out to be a counter, so with curved chrome, if you wait for 20 seconds, it goes 11, and in the brain, and so 20. That is, chrome counts more slowly. - Roman Dolzhenko Nov.
|