Re: Call for Adoption: Region Capture specification

I think the use case is worth fixing, but I have concerns with the current API shape.

In general, it seems to me that region capture is not needed for getViewPortMedia and requires Capture Handle for getDisplayMedia.
Therefore, it seems better to work on:
- getViewPortMedia: in particular how it can select the parts to capture potentially dynamically.
- capture handle to hook up capturing and captured pages for getDisplayMedia, then on how captured page can express its preferred regions worth being cropped to.

For getViewPortMedia, dynamic capture can be done with element references, IDs or element classes so that changing the DOM or element attributes impact getViewPortMedia results.
For getDisplayMedia, if we want to go there, it seems more meaningful to let the captured page tell the User-Agent which regions might be of interest to be cropped, possibly in advance, with origin safeguards/opt-ins... The User-Agent can then directly expose this information in the capturing page (using CaptureHandle) and let the capturing page decide which regions to select.

That is why I object to adoption of Region Capture at this stage.

Thanks,
	Y

> On 9 Dec 2021, at 16:01, Jan-Ivar Bruaroey <jib@mozilla.com <mailto:jib@mozilla.com>> wrote:
> 
> I support adoption of the Region Capture specification as a WEBRTC WG work item.
> 
> I'd prefer if the feature was kept to getViewportMedia where it lets applications crop to a page it has direct control over, which makes a lot of sense.
> 
> It seems less of a good fit in getDisplayMedia's tab capture as currently implemented in most browsers, where it risks exacerbating potential user confusion over what's being captured: the current document as opposed to all navigation in the containing tab. It's really the latter that is being captured, and a cropping feature in this context doesn't make a lot of sense, and becomes overly complicated. If it's implemented there, I hope it will be temporary and that we can eventually move to a safer, less confusing model over time.
> 
> On Mon, Nov 29, 2021 at 7:16 PM Bernard Aboba <Bernard.Aboba@microsoft.com <mailto:Bernard.Aboba@microsoft.com>> wrote:
> This is a Call for Adoption (CfA) of the Region Capture specification: 
> https://eladalon1983.github.io/region-capture/ <https://eladalon1983.github.io/region-capture/>
> The Github Repo is here: https://github.com/eladalon1983/region-capture <https://github.com/eladalon1983/region-capture>
> In response, please state one of the following:
> 
>   *   I support adoption of the Region Capture specification as a WEBRTC WG work item.
>   *   I object to adoption of Region Capture, due to issues filed in open bug <#number>
> 
> The CfA will end on December 13, 2021 at midnight Pacific Time.
> 
> Bernard
> 
> For the Chairs
> 
> 
> 
> -- 
> .: Jan-Ivar :.