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: Elad Alon via GitHub <sysbot+gh@w3.org>
Date: Mon, 23 May 2022 17:10:35 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1134932262-1653325833-sysbot+gh@w3.org>
> in the face of me clearly explaining them (having to reevaluate state assumptions, fueling the proliferation of unnecessary async, non-idiomatic JS confusing web devs into thinking the API does more than it does, and finally, performance)

I've asked you for the downsides. To your mention of these specific downsides, I [answered](https://github.com/w3c/mediacapture-region/issues/17#issuecomment-1132746253):
1. Let's use `cropTarget(Element)` in the same document - no **new** asynchronicity.
2. Let's use the other API when posting to another document - posting a message is asynchronous **anyway**. And if your **sender** is synchronous - which is unlikely - let it just painlessly use `setTimeout(async...)`. It's barely noticeable to the sender, and completely invisible to the receiver.

GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/17#issuecomment-1134932262 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:10:36 UTC

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