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

Re: [mediacapture-region] What makes CropTarget special to require an asynchronous creation? (#17)

From: Elad Alon via GitHub <sysbot+gh@w3.org>
Date: Thu, 03 Feb 2022 21:28:39 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1029418862-1643923718-sysbot+gh@w3.org>
> [cropTo](https://w3c.github.io/mediacapture-region/#dom-browsercapturemediastreamtrack-cropto) already returns a promise, so querying "all" documents in the single viewport captured to identify the crop target, seems reasonable to me.

I think you mean "browsing context" where you said "viewport".
Do you have a reasonable limit on how many different documents could be embedded in that browsing context?

> Cost to implementers is low on the [priority of constituencies](https://www.w3.org/TR/html-design-principles/#priority-of-constituencies) when it comes to shaping APIs.

Cost to implementers is low priority, but non-zero. It's only a problem if accommodating implementers comes at a non-trivial cost to a higher-priority constituency. Does it?

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

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 February 2022 21:28:41 UTC

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