- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 May 2022 12:33:26 +0000
- To: public-webrtc-logs@w3.org
> The same thing as if the user had chosen a different tab in the first place? Yes, these are similar issues. (But not identical - failure to take off is not the same as crashing mid-flight.) Does it matter though? Should our inability to fix one issue prevent us from addressing the other? We had good reasons to force a full selection on the user even when the application does not want it. Do we have a good reason to mandate that source-changing would either be supported **always** or **never**? Why not allow it to fit the app's needs? > Is a "Share this tab instead" button only a problem for apps that want to limit users to self-capture? I don't think so, but it is the clearer case, and the one that most concerns me. So let's keep things simple and stick with self-capture initially. > If so, I'm not supportive of apps using getDisplayMedia in this way, and opposed to new APIs to aid such use. Could you elaborate why? I am cognizant of our previous discussions on adjacent topics. For example, I don't think they apply here. This does not push the user towards self-capture to begin with, and does not prevent the user from stopping the capture. So those probably aren't your concerns. What are your concerns, then? -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/223#issuecomment-1122331602 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 10 May 2022 12:33:27 UTC