KhronosGroup / KhronosGroup/WebGL
Sync WEBGL_video_texture proposal with HTMLVideoElement.requestAnimationFrame proposal
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 2.9k
- Forks
- 704
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 4
Description
In https://github.com/dalecurtis/video-animation-frame/blob/master/explainer.md @dalecurtis is proposing, and has prototyped, a requestAnimationFrame callback on video elements. This seems to work well for applications that want to update at the video's frame rate.
In that proposal a VideoFrameMetadata dictionary is being proposed. It would be ideal to synchronize the WEBGL_video_texture proposal with that one, and ideally, just refer to that VideoFrameMetadata dictionary if that API moves forward in the standards process.
CC @shaoboyan .
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked video-animation-frame explainer.md and the WEBGL_video_texture proposal to compare their proposed metadata. Done means the WebGL proposal is synchronized with the HTMLVideoElement.requestAnimationFrame proposal and can refer to VideoFrameMetadata if that API advances.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- computer-graphics, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100