- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Feb 2023 00:41:24 +0000
- To: public-webrtc-logs@w3.org
The use case as presented would seem solved by a simple event fired *before* a page is navigated in a captured tab. Why can't a user agent do that? Then pausing isn't necessary, and the API is super simple. If we accept pausing is necessary, my preference would be to: 1. Reuse the track `mute` and `unmute` UA events for this (relax the "[black frame](https://w3c.github.io/mediacapture-main/getusermedia.html#track-muted)" requirement for video by some ms) 2. Add some means for JS to distinguish the cause of the UA mute 3. Add `track.unmute()` and align it with https://github.com/w3c/mediacapture-extensions/issues/39 6. Put the opt-in on [CaptureController](https://www.w3.org/TR/screen-capture/#dom-capturecontroller). This would accomplish several things: - Reuses the existing MediaStreamTrack API which needs to make sense for [a lot of sources](https://docs.google.com/presentation/d/10myL8D_a3oQghAH1RO522x00KO4qmGi9ZQyXQD70Xto/edit#slide=id.ga38008d958_3_120). - Keeps screen-capture specific controls to CaptureController. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/255#issuecomment-1439277125 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 February 2023 00:41:26 UTC