- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Tue, 24 Mar 2020 11:17:11 +0000
- To: public-webrtc-logs@w3.org
A powerful reason for a potential "user-chooses" API is that it works straight out of the box - no need to partially implement picking logic in the application - and that, if we get it right, we could guarantee consistent prompting behavior across browsers. Besides, if the prompt is actually good enough to do its job, why would prompting be a problem? If the user is to choose, why would letting the user choose be a problem? I would argue that there is a difference between an undesirable superflous yes/no re-prompt when the application has already done the choosing for you and a prompt that is actually selecting something that the user wants to select (and would otherwise select inside of application picker logic). All of my reasoning though is based on sometime in the future deprecating the old way. If we give up on that then making a suboptimal API is an option. But if it's optional, even far down the road, then we haven't really addressed the privacy concerns. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/669#issuecomment-603180084 using your GitHub account
Received on Tuesday, 24 March 2020 11:17:13 UTC