- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Nov 2023 16:29:19 +0000
- To: public-webrtc-logs@w3.org
>Is the following a fair summary? > > * @eladalon1983 prefers early decision (simpler to implement, no real web dev need) > * @jan-ivar prefers late decision (more convenient for web devs, prevent UA from not showing switch UI) Not completely fair, because it was never claimed that Web developers "need" early-decision; it was claimed that it's "sufficient" for them while making things easier for everyone else. But I am willing to lean in and actually claim it. Yes, developers **need** the early-decision, because cross-surface-type(!) source-injection is a footgun. Consider the code in this fiddle: https://jsfiddle.net/eladalon/Ly8a3wcs/ The "catch" here is that existing apps record app-state immediately after gDM resolves, and they never re-examine this state, because for several years now, this was good enough, since the surface-type could not change past that point. > Additional question related to how switching would actually work. Say we have the following case: > > * gdm, only one video track V1 > * switch -> one video track V2 and one audio track A1. > * switch -> one video track V3 > * switch -> one video track V4 and one audio track A2. > > In that case, we are expecting V1 to get the content of V2, V3 and V4. I am unclear about A1 and A2. Are we expecting that A1 does get migrated or not? What if A1 was exposed as part of gdm call? If migrating, what happens to A1 when V3 is live? It might be best to reduce the scope to only supporting migrating the first video track generated by gdm. All of this would be trivially and **predictably** handled with a `setSwitchCallback()` approach that does **not** offer source-injection. (That is - source-injection only offered if `setSwitchCallback()` isn't called.) -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/255#issuecomment-1819402706 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 20 November 2023 16:29:21 UTC