- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Oct 2024 01:39:23 +0000
- To: public-webrtc-logs@w3.org
> The web page can stop the old tracks anyway What enforces that the website can't keep both the old live injected track and the live new track? We need to specify this implicit action at a distance. > 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...) If this means there's one place where you decide what happens with the old tracks (enforced by the aforementioned action at a distance), then I agree that might be a good reason for a callback. Can we make it a settable attribute at least? -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share-extensions/issues/4#issuecomment-2390328892 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 October 2024 01:39:24 UTC