I tested how requestAnimationFrame() and nsRefreshDriver with moz log "nsRefreshDriver" and with the following sample. https://mdn.github.io/webgl-examples/tutorial/sample4/ When a window is occluded with enabling window occlusion tracking, period of requestAnimationFrame() and nsRefreshDriver were gradually longer and stopped finally. How they worked was same to when a window was minimized. It seems to related why a lot of tests were timed out. - https://searchfox.org/mozilla-central/rev/a82dd14b6bc3d05a6a3facc126607e6d34cc2f53/layout/base/nsRefreshDriver.cpp#939 ------------------------------------------------------- inactive timer next tick in 1000.000000 ms inactive timer next tick in 2000.000000 ms inactive timer next tick in 4000.000000 ms inactive timer next tick in 8000.000000 ms inactive timer next tick in 16000.000000 ms inactive timer next tick in 32000.000000 ms inactive timer next tick in 64000.000000 ms inactive timer next tick in 128000.000000 ms inactive timer next tick in 256000.000000 ms inactive timer next tick in 512000.000000 ms inactive timer next tick in 1024000.000000 ms stopped to tick
Bug 1688997 Comment 18 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I tested how requestAnimationFrame() and nsRefreshDriver with moz log "nsRefreshDriver" and with the following sample. https://mdn.github.io/webgl-examples/tutorial/sample4/ When a window is occluded with enabling window occlusion tracking, period of requestAnimationFrame() and nsRefreshDriver were gradually longer and stopped finally. How they worked was same to a background tab of active window and front tab of minimized window. It seems to related why a lot of tests were timed out. - https://searchfox.org/mozilla-central/rev/a82dd14b6bc3d05a6a3facc126607e6d34cc2f53/layout/base/nsRefreshDriver.cpp#939 ------------------------------------------------------- inactive timer next tick in 1000.000000 ms inactive timer next tick in 2000.000000 ms inactive timer next tick in 4000.000000 ms inactive timer next tick in 8000.000000 ms inactive timer next tick in 16000.000000 ms inactive timer next tick in 32000.000000 ms inactive timer next tick in 64000.000000 ms inactive timer next tick in 128000.000000 ms inactive timer next tick in 256000.000000 ms inactive timer next tick in 512000.000000 ms inactive timer next tick in 1024000.000000 ms stopped to tick
I tested how requestAnimationFrame() and nsRefreshDriver with moz log "nsRefreshDriver" and with the following sample. https://mdn.github.io/webgl-examples/tutorial/sample4/ When a window is occluded with enabling window occlusion tracking, period of requestAnimationFrame() and nsRefreshDriver were gradually longer and stopped finally. How they worked was same to a background tab of active window and a front tab of minimized window. It seems to related why a lot of tests were timed out. - https://searchfox.org/mozilla-central/rev/a82dd14b6bc3d05a6a3facc126607e6d34cc2f53/layout/base/nsRefreshDriver.cpp#939 ------------------------------------------------------- inactive timer next tick in 1000.000000 ms inactive timer next tick in 2000.000000 ms inactive timer next tick in 4000.000000 ms inactive timer next tick in 8000.000000 ms inactive timer next tick in 16000.000000 ms inactive timer next tick in 32000.000000 ms inactive timer next tick in 64000.000000 ms inactive timer next tick in 128000.000000 ms inactive timer next tick in 256000.000000 ms inactive timer next tick in 512000.000000 ms inactive timer next tick in 1024000.000000 ms stopped to tick