- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Oct 2024 23:39:22 +0000
- To: public-webrtc-logs@w3.org
> My thinking is a `sourceswitch` event that fires whenever the user switches source (with no requirement to stop tracks) The callback approach allows this as well. I was not clear about it previously in this thread (sorry about that), setting the callback would not be a signal for the UA to go to the switch mode and stop the previous tracks. Instead, we stick with the injection model for old tracks. The web page can stop the old tracks anyway. I am ok adding an option so that the web page tells the UA to stop the tracks (hence the various proposals I made on top of the callback). We need though language that instructs that media is not flowing in the old tracks until the callback is executed. Having a callback to deliver the stream is better since there is one place where you decide what to do with the new tracks (clone it, stop it...). And the spec can be made clear that MediaStreamTracks are not created if the callback is not set. This is more difficult with events. And I do not really see a case for multiple event listeners for this switch case (web devs already have configuration change anyway). -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share-extensions/issues/4#issuecomment-2389983592 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 October 2024 23:39:23 UTC