- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Feb 2023 22:33:37 +0000
- To: public-webrtc-logs@w3.org
> Both Chrome and Safari now allow the user to change what surface is captured. I applaud user-agent-centered features like this! — I like how they tend to keep the end-user in charge. But before exposing APIs for apps to potentially wrest control over such user-initiated changes, I'd like to understand the concrete problems that require app intervention, since gating output on the app seems directly counter to the user's wishes to inject different input. What needs cannot be met without pausing? > * What if an application intends to do some processing that depends on the captured content? What processing would this be? What app would e.g. blur screen capture? > * What if an application wants to set different constraints, for instance when capturing a window vs. when capturing a screen? What constraints would this be? Since a window may be resized by the end-user, and be larger or smaller than a monitor, an app that only reacts to such changes upon source-switching would seem to have the wrong idea. > * What if the application intends to save different surfaces to different files, and wants to start appending to a new file whenever the user changes the source? That application can add buttons for the user to do exactly that. What if the user intends to save different surfaces to the same file, using this user agent feature? -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/255#issuecomment-1433810318 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 16 February 2023 22:33:39 UTC