> 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](https://w3c.github.io/mediacapture-region/#dom-mediadevices-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](https://github.com/w3c/mediacapture-region/issues/17). 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 https://github.com/w3c/mediacapture-region/issues/11#issuecomment-1126319737 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Friday, 13 May 2022 18:21:50 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:57 UTC