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

> it seems to me that: The element ID based solution won't enable the captured app to know of cases where the crop failed

@yoavweiss neither will [produceCropTarget]( which infallibly mints an opaque element reference that can be postMessaged. It exposes no cropping related information, and pages can't learn whether they're being captured or cropped to from it; it's related to cropping in name only.

> The former is also the reason why the handle creation [needs to be async](

There's no such inherent need for it to be async; this would solely be a convenience for some browser implementers.

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Friday, 13 May 2022 18:21:50 UTC