Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)

> > what cost do users and developer incur, if the API is made asynchronous?
> 
> @eladalon1983 I already answered that above in [#11 (comment)](https://github.com/w3c/mediacapture-region/issues/11#issuecomment-1126528615) and [#11 (comment)](https://github.com/w3c/mediacapture-region/issues/11#issuecomment-1126934670).

Those comments criticize the current API shape from multiple directions, but do not explain how accommodating implementers here, would come at the expense of higher constituencies. Unless you mean to say that developer confusion is your claim of harm to higher constituencies? Is that your argument? If so - is it your only argument wrt priority of constituencies, or are there more?

-- 
GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/11#issuecomment-1128554988 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 17 May 2022 08:11:09 UTC