- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Fri, 07 Jan 2022 09:27:28 +0000
- To: public-webrtc-logs@w3.org
> I interpreted as an attempt to make this work outside of known pairs of sites. If we want it to work with capture of all tabs (aka getDisplayMedia), I think this is desirable. At least we should have a specific discussion on this. If we want it to work for self view only and do not plan in a near future to support the general case, I can understand we do not need that. In such a case, as we discussed before: - it makes sense to me to start with a getViewPortMedia specific solution. - getViewPortMedia can support cropping without introducing a separate region capture API. Hence my desire to first nail down the scope and the use cases before diving in API design. > for capturer-side features like cropping, I prefer tight coupling for the reason I stated. Once we nail down the scope, I'd like to get deeper into that. I do not believe the bank example is meaningful: the capturee proposes some cropping regions of interest and the capturer applies the cropping or not (and which cropping) depending on its level of interest/understanding/trust. Similarly, capturee (the source) can provide low res and high res camera capture and it is up to the capturer to decide what best suites its needs. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/195#issuecomment-1007259750 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 7 January 2022 09:27:29 UTC