[Webkit-unassigned] [Bug 95360] DisplayRefreshMonitorManager::registerClient fails to register client

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=95360





--- Comment #2 from Arvid Nilsson <anilsson at rim.com>  2012-08-29 11:48:24 PST ---
It looks to me like it would be a problem if you managed to get two ScriptedAnimationController instances to request animation frames. The second one would fail to register with the monitor.

I'll see if I can put together something that manages to do that (it may be impossible due to more high level mechanisms, not sure).

The reason I ran into this is not a specific bug, but development on a new feature for the BlackBerry port, perform accelerated compositing sync on a requestAnimationFrame instead of a 0-timeout timer. The idea is to service all the JS animations first, and then perform the AC sync last, to make sure their most recent animation changes become visible immediately.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.