- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Feb 2020 21:29:01 +0000
- To: public-webrtc-logs@w3.org
> However, it is not clear to me how a promise-based method actually deals with the resource competition issue. It doesn't. And that's not why the proposal changed into using a promise. This was in response to privacy issues. An asynchronous API has the possibility of gating its return value behind a permissions prompt, should we want to. This issue is not about tackling the existing privacy concerns in general, but as to not leak more device info in a synchronous API. However if this API actually had a prompt, you would be less likely to want to use it for legitimate purposes, since the permissions prompt would likely be too confusing for real users. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/21#issuecomment-589842904 using your GitHub account
Received on Friday, 21 February 2020 21:29:03 UTC