Closed youennf closed 4 months ago
@youennf Why? (I'm not opposed, just would like to know where this came up).
Naively, I'd expect streams to be useful only to access older (main-thread only) APIs?
Naively, I'd expect streams to be useful only to access older (main-thread only) APIs?
If we want to expose WebAudio or RTCPeerConnection APIs to workers, it is convenient to have MediaStream available there. And it should not be a big deal to implement.
At the moment, the only purpose would be to reuse libraries of JS code that already use MediaStreams. We don't have any objects exposed that have MediaStream in their interface. We should probably submit this when we have the proposal to import such an interface to Worker.
https://github.com/w3c/mediacapture-fromelement/issues/65 would be a reason to merge this.
This issue had an associated resolution in WebRTC February 2024 meeting – 20 February 2024 (Expose MediaStream in Workers):
RESOLUTION: Exposing MediaStream in workers is reasonable but low priority
Preview | Diff