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

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

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Thu, 26 May 2022 20:53:16 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1139035402-1653598394-sysbot+gh@w3.org>
> > > @youennf getting the irrelevant `MediaDevices` object out of the picture is a win. Thanks!
> > 
> > @jan-ivar, does that mean that if I send a PR to move the point of exposure to CropTarget.fromElement(Element), you'll approve it? Note that I'll keep it async, **which is the status quo**, and maintain the same **note** about it being a contested issue.
> That seems like a good way to separate these issues.

@eladalon1983 the way I interpreted the compromise above was we agreed to move the point of exposure from MediaDevices (a SecureContext object) to CropTarget (which is not). Adding `SecureContext` to fromElement would appear to not honor that.

> The status quo of the document is to only expose token-minting in secure contexts.

@youennf already mentioned in https://github.com/w3c/mediacapture-region/issues/11#issuecomment-1073988276 that this was part of the issue: _"MediaDevices is SecureContext, Element is not. It seems ok for a non secure document to be able to create a CropTarget"_, so these were known stakes.

> Relaxing restrictions is always backwards compatible; tightening them is not.

@alvestrand In the interest of progress, I'll accept the PR with a note on the lack of consensus over SecureContext.

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

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 May 2022 20:53:17 UTC

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