168111 2017-02-10 01:52:59 -0800 Make requestAnimationFrame use the new animation controller 2017-06-15 13:50:05 -0700 1 1 1 Unclassified WebKit Animations Safari Technology Preview Unspecified Unspecified NEW https://bugs.webkit.org/show_bug.cgi?id=167899 InRadar P2 Normal --- 1 graouts webkit-unassigned dino mark webkit-bug-importer oldest_to_newest 1275264 0 graouts 2017-02-10 01:52:59 -0800 As part of the work towards a single animation controller (https://bugs.webkit.org/show_bug.cgi?id=167899), we will need to migrate requestAnimationFrame to use it. 1275265 1 webkit-bug-importer 2017-02-10 01:54:53 -0800 <rdar://problem/30461684> 1319693 2 mark 2017-06-15 13:50:05 -0700 An additional consideration is to make sure the new animation controller has a migration path to HTML 5.2 variable refresh rate standards, seen at https://github.com/w3c/html/issues/375 -- ala GSYNC, FreeSync, HDMI 2.1 VRR, VESA Adaptive-Sync (And possibly future versions of Apple ProMotion that supports dynamic VRR). e.g. Sychronizing refresh rate to the rate of animations of the dominant full screen canvas (e.g. 45fps makes the screen run at 45Hz), for <VIDEO>, for WebGL, and for Canvas2D.