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

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

From: youennf via GitHub <sysbot+gh@w3.org>
Date: Thu, 27 Jan 2022 09:17:50 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1023001792-1643275069-sysbot+gh@w3.org>
> without costing anything for other browser

A promise has a cost for web developers and for devices executing them.
We should not overpromisify APIs.

> Who is C in this scenario?

C is the process producing the screen frames and is the one that needs to identify the actual display layer the element refers to. My understanding is that this process is separated from A and B.

> B will call cropTo directly.

cropTo is already an asynchronous operation and can handle the resolution of CropTarget.

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

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 January 2022 09:17:52 UTC

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