Re: Call for Consensus (CfC) on Issue 17 of "Region Capture"

CropTarget production should be synchronous.

Proof has been made that this API is implementable as a synchronous API without any particular hurdle.
Web developers convenience prime UAs developers convenience.
We also have sufficient experience to make such decision, I do not buy the ‘we never know’ argument.


> On 12 Jul 2022, at 09:34, Bernard Aboba <Bernard.Aboba@microsoft.com> wrote:
> 
> This is a Call for Consensus (CfC) on Issue 17 of "Region Capture". 
> 
> Section 6.2 of the "Region Capture" specification contains a Note: 
> 
> 
> 
> Issue 17 of "Region Capture" is available here: 
> What makes CropTarget special to require an asynchronous creation? · Issue #17 · w3c/mediacapture-region · GitHub <https://github.com/w3c/mediacapture-region/issues/17>
> 
> The Discussion of Issue 17 at the June 23 Virtual Interim is available here: 
> WEBRTCWG-2022-06-23 - Google Slides <https://docs.google.com/presentation/d/1-SgzfMAeVG3u5vErJncC7OKDTGNDzSOMg_78LP8SULk/edit#slide=id.g131149eddb2_0_0>
> 
> Minutes of the June 23 Virtual Interim are here: 
> https://www.w3.org/2022/06/23-webrtc-minutes.html <https://www.w3.org/2022/06/23-webrtc-minutes.html> 
> 
> In replying to this CfC, respondents should indicate one of the following:
> 
> * CropTarget production should be synchronous.
> * CropTarget production should be asynchronous.
> 
> The CfC will last until July 26, 2022 at midnight Pacific Time. 
> 
> Bernard
> For the Chairs