- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Fri, 29 Sep 2023 08:03:17 +0000
- To: public-webrtc-logs@w3.org
Topic was discussed yesterday and it seems there is some convergence. AIUI, the proposal is: - An event is fired (or a callback is executed) to tell web app that surface switching happens. - The UA makes sure to not provide any media to the old and new tracks until the event/callback is fired/executed. - The event/callback exposes new audio/video tracks depending on the user selection. - When firing/execution is done, the UA ends the old tracks. - The UA starts providing media on the new tracks. All these steps are synchronously executed. @eladalon1983, @jan-ivar, can you clarify whether this is a correct summary? If this is correct, we should consider removing step 4 (closing the old tracks). The web application could decide to stick with the old tracks and stop the new tracks instead if it is thought more adequate. This would allow easy migration in the simple cases (just do nothing for video, check for new audio). We could have a simple CaptureController `onswitch` event, given it would not have any side effect. We could in the the future extend the event with a `waitUntil` API if we think the web app needs more time to decide what to do before the UA starts generating media. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/255#issuecomment-1740477003 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 29 September 2023 08:03:20 UTC