Looks like this call is on the window and if it is used the client will assume that the engine wants the same frame rate as the client.

Two ways to possibly deal with this, one would be to add a WebSetting to blink so the callback is queued but it does not schedule an animation, https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit/Source/core/dom/ScriptedAnimationController.cpp&l=85. If a user gesture triggers an update from the engine the callback will run as usual.

The other would be to simply stop the engine from requesting any commits if it has been put in "paused" state, which would naturally pause these requests as well. Since commit requests are done inside the cc channels, we would need a component which is aware of when we are in this state that the channel on the engine can talk to.

Obsolete, WontFix.