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

How to handle specs that extend MediaStreamTrack, in particular MediaStreamTrack slots? #1004

Open
youennf opened this issue May 30, 2024 · 2 comments

Comments

@youennf
Copy link
Contributor

youennf commented May 30, 2024

mst content h defines a content hint extension to MediaStreamTrack.
But it does not define what should be done when cloning or transferring the track.
We should try to solve this.

@youennf
Copy link
Contributor Author

youennf commented May 30, 2024

One solution, mentioned by @jan-ivar is to define transfer and clone steps.
Then extension specs can add transfer/clone steps dedicated to their extension slots.

@jan-ivar
Copy link
Member

Note this is about extension through partial interface MediaStreamTrack which seems largely editorial.

But a similar problem appears to exist with extension through inheritance, e.g. w3c/mediacapture-fromelement#96 but that's perhaps separate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants