Intent to Implement: HTMLVideoElement.requestAnimationFrame()

[Thomas Guilbert]

Contact emails tgui...@chromium.org Explainer https://github.com/dalecurtis/video-animation-frame/blob/master/explainer.md Design docs/spec

N/A. TAG review https://github.com/w3ctag/design-reviews/issues/429 Summary HTMLVideoElement.requestAnimationFrame() registers a one-shot callback, called after a video frame has been presented for composition. It also provides useful metadata about that frame. Motivation This features allows web applications that use WebGL or <canvas> with <video> to composite at the video rate rather than the display rate. It also allows for reliable video metadata which can be correlated with other page events (e.g. user inputs) and used for automated analysis. It also allows frame-accurate web-platform-tests. Risks

Interoperability and Compatibility There are few signals from other browsers. Firefox: No public signals Edge: Public support (https://discourse.wicg.io/t/proposal-video-requestanimationframe/3691/6) Safari: No public signals Web developers: No signals

Ergonomics

The callback can delay the release of frames, which might have some performance implications (i.e slowing down HW decoding).

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? Yes Is this feature fully tested by web-platform-tests? N/A.

Link to entry on the Chrome Platform Status https://www.chromestatus.com/feature/6335927192387584

Requesting approval to ship?

No.