- From: Tove Petersson via GitHub <sysbot+gh@w3.org>
- Date: Mon, 21 Oct 2024 13:07:13 +0000
- To: public-webrtc-logs@w3.org
tovepet has just created a new issue for https://github.com/w3c/mediacapture-screen-share-extensions: == Auto-pause for Captured Surface Switching (2nd edition) == _Note: This is a new issue separated out from https://github.com/w3c/mediacapture-screen-share-extensions/issues/4_ Some browsers allow users to switch an ongoing screen-capture to instead share another surface. When this happens, applications may need to react to the change of surface to, e.g., * adapt the UI for different surface types * set up crop targets for Region Capture For some applications it is also important to separate frames delivered for one surface from frames delivered for another source, e.g., if recording different surfaces to different files. To solve these issues, we propose the following: 1. An event is added to the `CaptureController` that is emitted each time a user has switched to a new captured surface: ``` controller.addEventHandler('surfaceswitch', ...); ``` 2. An `autoPause` option is added to `getDisplayMedia`: ``` getDisplayMedia({..., autoPause: true}); ``` If `autoPause` is `true`, a surface switch goes through the following steps: 1. Stop emitting frames on all tracks associated with the capture. 2. Set `enabled = false` for all tracks associated with the capture. 3. Update all tracks associated with the capture to the new surface. 4. Fire the `surfaceswitch` event. Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share-extensions/issues/15 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 21 October 2024 13:07:14 UTC