W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > February 2022

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

From: youennf via GitHub <sysbot+gh@w3.org>
Date: Tue, 08 Feb 2022 09:56:42 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1032420017-1644314201-sysbot+gh@w3.org>
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 https://github.com/w3c/mediacapture-region/issues/11#issuecomment-1032420017 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 8 February 2022 09:56:44 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:56 UTC