- From: Tove Petersson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Oct 2024 15:05:47 +0000
- To: public-webrtc-logs@w3.org
@youennf:
> ...
> 2. We start simple (`captureController.processSourceSwitch(callback)`) and extend the API when we are ready.
>
> Isn't option2 somehow equivalent to one of these option 2 extensions ?
>
> 1. `captureController.processSourceSwitch(callback, { mode: 'stop-previous-tracks' })`
In the case of requesting surface tracks, it's equivalent to this one.
So, if I understand you correctly, you think we could start with something like the following?
An application can register a callback and specify the stop-previous-tracks-mode:
```
captureController.processSourceSwitch(callback, { mode: 'stop-previous-tracks' });
getDisplayMedia({captureController, …});
```
And then, when a user selects another surface, the UA will:
1. stop the tracks for the previous surface
2. call the callback with a new stream for the surface the user has selected.
This sounds good to me.
--
GitHub Notification of comment by tovepet
Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share-extensions/issues/4#issuecomment-2386262124 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 October 2024 15:05:48 UTC