- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Mon, 16 May 2022 07:56:26 +0000
- To: public-webrtc-logs@w3.org
> Let's discuss async in #17. That is a good idea, this thread is very difficult to follow, partially duet fact it is going in plenty of directions and touching so many subjects. With regards to sync/async, @yoavweiss provided some more input on why it might be good to go with async, but I did not understand these points. Could they be elaborated in issue #17? I filed a specific issue to discuss the opaque object vs. string issue: https://github.com/w3c/mediacapture-region/issues/46. If we go back to this particular issue (Why expose produceCropTarget at MediaDevices level?), let's try a summary. 1. Main argument for having it in MediaDevices is that this API is media related so having this API in a media related location makes sense. 2. Main argument for moving to Element is that this API is only about Element and does not need MediaDevices at all. This for instance creates some corner cases we should try to avoid, like calling produceCropTarget on a neutered MediaDevices (https://jsfiddle.net/8a0qsf35/). -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/11#issuecomment-1127349517 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 16 May 2022 07:56:27 UTC