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

Where do we spec WebGPU-WebCodecs interaction? #2498

Closed
kainino0x opened this issue Jan 12, 2022 · 3 comments · Fixed by #4063
Closed

Where do we spec WebGPU-WebCodecs interaction? #2498

kainino0x opened this issue Jan 12, 2022 · 3 comments · Fixed by #4063
Projects
Milestone

Comments

@kainino0x
Copy link
Contributor

Extracted from #2124.

I proposed spec text in w3c/webcodecs#412 which put it in WebCodecs. WebGPU group was OK with this direction if the WebCodecs group accepted it.


Feedback on w3c/webcodecs#412 has been negative on including this functionality in WebCodecs when it is clearly a part of WebGPU that interacts with WebCodecs and not the other way around. From that thread:

It's fine not to implement a specification in its entirety, it's fairly common.

Though I agree this is common, I know Apple has taken a hard stance against this as they intend to implement 100% of the WebGPU spec with no omissions. @litherum how do you view the tradeoff between that intent and the problem of "monkey patching" WebGPU from the WebCodecs spec?

@kainino0x kainino0x added this to the V1.0 milestone Jan 12, 2022
@kainino0x kainino0x added this to Needs Discussion in Main Jan 12, 2022
@dalecurtis
Copy link

FWIW, VideoFrame is already referenced in the HTML and WebGL specs. A method signature which takes a typedef of HTMLVideoElement or VideoFrame seems pretty harmless for specifying type specific interactions.

@kdashg
Copy link
Contributor

kdashg commented Jan 13, 2022

Post V1 please!

@kainino0x
Copy link
Contributor Author

Depending on the resolution to #2301 I'm happy to just put this in an extension doc in our repo. Ideally I'd like to land a draft somewhere and that seems like a nice place for it, if we allow this kind of thing in that directory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Main
Needs Discussion
4 participants