- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Oct 2024 20:35:00 +0000
- To: public-webrtc-logs@w3.org
> A callback might be better instead so that there is only one receiver that is responsible to ... closing the new ...tracks. > It makes sense for the application to be responsible to stop a track that it has requested, but in this case the UA throws an extra track on the application that that the application doesn’t want. It seems wrong to me to force application writers to stop this extra track that they never asked for. Forgetting stop seems a problem in all the proposals. What if the UA stopped tracks synchronously after the callback/event-handler, requiring JS that wants to use a track to clone it? @youennf is stop problem the only issue driving you to prefer callbacks over events? -- 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-2389649526 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 20:35:01 UTC