Bug 168111 - Make requestAnimationFrame use the new animation controller
Summary: Make requestAnimationFrame use the new animation controller
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Animations (show other bugs)
Version: Safari Technology Preview
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2017-02-10 01:52 PST by Antoine Quint
Modified: 2017-06-15 13:50 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Antoine Quint 2017-02-10 01:52:59 PST 
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.
Comment 1 Radar WebKit Bug Importer 2017-02-10 01:54:53 PST 
<rdar://problem/30461684>
Comment 2 mdrejhon 2017-06-15 13:50:05 PDT 
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.