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.

Sign up for GitHub

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

Jump to bottom

Spec should link to https://www.w3.org/TR/webcodecs/#close-videoframe instead of calling close() #91

Closed
youennf opened this issue Jan 19, 2024 · 0 comments · Fixed by #102
Closed

Spec should link to https://www.w3.org/TR/webcodecs/#close-videoframe instead of calling close() #91

youennf opened this issue Jan 19, 2024 · 0 comments · Fixed by #102

Comments

@youennf
Copy link
Contributor

youennf commented Jan 19, 2024 •
edited
Loading

The spec says:

The [WritableStream](https://streams.spec.whatwg.org/#writablestream) accepts [VideoFrame](https://w3c.github.io/webcodecs/#videoframe) objects. When a [VideoFrame](https://w3c.github.io/webcodecs/#videoframe) is written to [writable](https://w3c.github.io/mediacapture-transform/#dom-videotrackgenerator-writable), the frame’s close() method is automatically invoked, so that its internal resources are no longer accessible from JavaScript.

Instead it should call the corresponding close algorithm.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Call VideoFrame Close algorithm instead of VideoFrame close method youennf/mediacapture-transform
1 participant
@youennf