- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Apr 2024 16:53:39 +0000
- To: public-webrtc-logs@w3.org
> where `video1` would be using the switch-track model and `video2` would be using the injection model. I like this idea of exposing both to the application and letting it use the one it prefers. It seems neutral and would let us measure over time whether apps find injection desirable, while remaining backwards compatible. With `preventDefault()` I was hung up on the UA needing to stop one or the other right away, but if we don't need that then it simplifies. My question would be what are the semantics now of calling `video2.srcObject.getVideoTracks()[0].stop()`? Would it also stop `video1.srcObject.getVideoTracks()[0]` or not (and vice versa)? 1. If no, the hardware light might stay on for several seconds after as user clicks stop (until GC) in today's apps unaware of the `newsource` event. 2. If yes, we've created a new "either-or" track, where stopping one stops both, which could confuse apps. Running with 2 for a bit, maybe we just fire `ended` on the other track and call it a special case? -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share-extensions/issues/4#issuecomment-2050114520 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 11 April 2024 16:53:41 UTC