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

It would be interesting to understand whether libraries actually go through all elements and get all their attributes.
I suspect that this would be a perf issue w/o CropTarget.

Thinking a bit more though, I don't see why the spec mandates to expose a single CropTarget per Element.
It makes implementations a bit harder without any real benefit. Maybe this is a left over from the CropID initial version?
Removing this constraint from the spec and making cropTarget a method (probably renaming it to getXYZ as well) seems like a good idea to me.

GitHub Notification of comment by youennf
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Tuesday, 8 February 2022 09:56:44 UTC