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

> As I've iterated before, I object to the excessive generality of posting element.id between contexts.

JS can already post element ids between contexts, and is not up for question here, so objecting to that seems out of scope.

> security, privacy and implementation considerations of ... such an API ...

@alvestrand Element id is an existing API, so I assume you mean [cropTo](https://w3c.github.io/mediacapture-region/#dom-browsercapturemediastreamtrack-cropto) here? Video cropping (whether from screen-share or camera) [is already possible](https://webrtc.github.io/samples/src/content/insertable-streams/video-crop/) in the platform. So what exactly are the security and privacy considerations of more reliable cropping to an element?

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


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

Received on Friday, 6 May 2022 13:39:59 UTC