Allow converting VideoFrame to RGB pixel formats by calling VideoFrame.copyTo() about standards-positions HOT 7 CLOSED

Yes, we should consider introducing VideoFrame.canCopyTo(), especially if we end up adding more format options to VideoFrameCopyToOptions

from standards-positions.

The use case is fine and the API is better than going through a canvas (more straightforward and async by nature).

from standards-positions.

This is a draft position. Unless anyone objects within a week we will change it to the official WebKit position.

@Djuffin, we discussed this proposal and we are "supportive" with a concern around the API Design.

The one thing that would be a nice addition is having some means to synchronously detect if copying to a colorspace would be possible without first needing to call .copyTo() (i.e., some kind of support check). We can see it's feasible to, for example, create a VideoFrame and perform support checks by seeing if it throws... but, to us, that feels like not so great developer ergonomics.

Have you thought about adding some kind of mechanism to check what colorspaces the browser supports?

from standards-positions.

VideoFrame.allocationSize() is synchronous and it throws if conversion is not supported.

from standards-positions.

Else, for inspiration, we just introduced ClipboardItem.supports('image/svg+xml') to the Clipboard API. A similar approach could be feasible here…

from standards-positions.

Note that WebIDL will drop dictionary member on the floor, so VideoFrame.canCopyTo() can't rely on dictionary (it could take an object though, and then iterate over the member names that way to reject on any unknown member name... and then check the details of each that is supported.)

from standards-positions.

Closing with "support" position. Please ping us on the W3C side when there's a PR for us to review!

from standards-positions.