Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTMLVideoElement.requestVideoFrameCallback() #494

Closed
2 of 3 tasks
ydaniv opened this issue Sep 26, 2023 · 7 comments
Closed
2 of 3 tasks

HTMLVideoElement.requestVideoFrameCallback() #494

ydaniv opened this issue Sep 26, 2023 · 7 comments
Labels
focus-area-proposal Focus Area Proposal

Comments

@ydaniv
Copy link

ydaniv commented Sep 26, 2023

Description

"The requestVideoFrameCallback() method allows web authors to register a callback that runs in the rendering steps when a new video frame is sent to the compositor. This is intended to allow developers to perform efficient per-video-frame operations on video, such as video processing and painting to a canvas, video analysis, or synchronization with external audio sources."

-- from web.dev article

This method enables authors to develop features that are impossible, for some cases, or cumbersome and inefficient at best.

Unfortunately, this is not yet an official W3C spec, and is still only a WICG draft.
However, it has already been shipped in Chrome/Edge and Safari for quite some time.

Another note: this spec has been reviewed and approved by TAG: w3ctag/design-reviews#429.

Specification

https://wicg.github.io/video-rvfc/

Open Issues

No response

Tests

https://wpt.fyi/results/video-rvfc?label=experimental&label=master&aligned

Current Implementations

  • Blink
  • Gecko
  • WebKit

Standards Positions

Was marked as ready to add here: mozilla/standards-positions#250
And also as worth prototyping.

Browser bug reports

No response

Developer discussions

No response

Polls & Surveys

No response

Existing Usage

No response

Workarounds

No response

Accessibility Impact

May improve performance and thus more power-friendly.

Privacy Impact

No response

Other

No response

@ydaniv ydaniv added the focus-area-proposal Focus Area Proposal label Sep 26, 2023
@AshleyScirra
Copy link

Also note it's not currently supported in Android WebView: https://bugs.chromium.org/p/chromium/issues/detail?id=1306926

@zcorpan
Copy link
Member

zcorpan commented Dec 21, 2023

Unfortunately, this is not yet an official W3C spec, and is still only a WICG draft.

Is there a plan to move this to a W3C WG/WHATWG?

@ydaniv
Copy link
Author

ydaniv commented Dec 24, 2023

Unfortunately, this is not yet an official W3C spec, and is still only a WICG draft.

Is there a plan to move this to a W3C WG/WHATWG?

Good question! @tomayac @tguilbert-google ?

@tguilbert-google
Copy link

I had plans to add this to the full HTML spec directly, following this comment, but didn't end up working on it.

Is the next step to move this to a W3C WG/WHATWG in order to "graduate" the spec, and then add it to the HTML spec?

@zcorpan
Copy link
Member

zcorpan commented Jan 3, 2024

Adding it to HTML is the same as moving to the WHATWG. 👍

@tguilbert-google
Copy link

Ok, thanks! I will work on this this quarter.

@dandclark
Copy link
Contributor

This proposal has been accepted as part of Interop 2024! On behalf of the entire Interop team, thank you for proposing it. You’ll be able to track progress on this topic throughout the year via the Interop 2024 dashboard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
focus-area-proposal Focus Area Proposal
Projects
Status: Done
Development

No branches or pull requests

5 participants