Skip to content

Allow allocationSize/copyTo on opaque VideoFrames when converting to RGB #1

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

Draft
Djuffin wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Allow allocationSize/copyTo on opaque VideoFrames when converting to RGB #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions index.src.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3830,7 +3830,7 @@
When invoked, run these steps:
1. If {{platform object/[[Detached]]}} is `true`, throw an
{{InvalidStateError}} {{DOMException}}.
2. If {{VideoFrame/[[format]]}} is `null`, throw a {{NotSupportedError}}
2. If {{VideoFrame/[[format]]}} is `null` and |options|.{{VideoFrameCopyToOptions/format}} does not [=map/exist=], throw a {{NotSupportedError}}
{{DOMException}}.
3. Let |combinedLayout| be the result of running the [=Parse
VideoFrameCopyToOptions=] algorithm with |options|.
Expand All @@ -3849,7 +3849,7 @@
When invoked, run these steps:
1. If {{platform object/[[Detached]]}} is `true`, return a promise rejected
with a {{InvalidStateError}} {{DOMException}}.
2. If {{VideoFrame/[[format]]}} is `null`, return a promise rejected with a
2. If {{VideoFrame/[[format]]}} is `null` and |options|.{{VideoFrameCopyToOptions/format}} does not [=map/exist=], return a promise rejected with a
{{NotSupportedError}} {{DOMException}}.
3. Let |combinedLayout| be the result of running the [=Parse
VideoFrameCopyToOptions=] algorithm with |options|.
Expand Down Expand Up @@ -6258,6 +6258,7 @@
conditions, such as allowing a site to mutate a codec input or output while
the underlying codec is still operating on that data. This concern is mitigated
by ensuring that input and output interfaces are immutable.
</div>

Privacy Considerations{#privacy-considerations}
===============================================
Expand Down Expand Up @@ -6305,6 +6306,7 @@
budget", which depletes as authors use WebCodecs and other identifying APIs.
Upon exhaustion of the privacy budget, codec capabilities could be reduced to a
common baseline or prompt for user approval.
</div>

Best Practices for Authors Using WebCodecs{#best-practices-developers}
======================================================================
Expand Down