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

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

From: Aziz Javed via GitHub <sysbot+gh@w3.org>
Date: Mon, 23 May 2022 17:12:58 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1134934556-1653325976-sysbot+gh@w3.org>
Hello there. Aziz Javed from Google Meet here, working with [Lindsay](https://github.com/w3c/mediacapture-region/issues/31) from Google Editors. We've already built a very significant feature based on this API's origin trial. I'm happy to inform y'all that we were not at all inconvenienced by the async nature of produceCropId. Exposure on MediaDevices vs. on CropTarget is likewise not at all a concern for us; either approach works. Generally speaking, all alternatives debated here are perfectly reasonable for us, so long as they're performant. We'd favor whichever API shape would allow this feature to be shipped in as many browsers as possible, as early as possible.

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

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 23 May 2022 17:12:59 UTC

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