- From: Sichao Xue (sichax) via GitHub <sysbot+gh@w3.org>
- Date: Mon, 10 Jun 2024 19:48:52 +0000
- To: public-webrtc-logs@w3.org
The work-around we have right now is very similar to your suggestion, the only difference is that instead of pausing remote transmission, we set the `track.enabled` to `disabled` when `captureHandle` is `null`, so the video stream is blank/black. ```js stream.getTracks().forEach(track=> track.enabled = false) ``` >The capture handle is indeed reset, and you'll get no capture handle until the refreshed page loads to the point where it sets it again. That's exactly what I wanted to confirm. Not sure if this is a common knowledge for web developer when cross-document navigation happens, it seems so. It might be helpful to add this behavior to the blog here: https://developer.chrome.com/docs/web-platform/capture-handle#:~:text=A%20cross%2Ddocument%20navigation%20occurs%20in%20the%20captured%20web%20app. For captured content switching. Since we manually set the `tract.enabled` to `false`, the result is quite similar to auto-pause feature you are proposing. It will be way more reliable if we can detect it from dedicated browser APIs. @eladalon1983 Thank you so much for your insights, you are very friendly and thoughtful. -- GitHub Notification of comment by xuesichao Please view or discuss this issue at https://github.com/w3c/mediacapture-handle/issues/74#issuecomment-2159165263 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 10 June 2024 19:48:53 UTC