W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > December 2019

Re: [mediacapture-main] In-content device selection a mistake. Too complicated, leaks info (#652)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Thu, 19 Dec 2019 00:17:39 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-567271467-1576714658-sysbot+gh@w3.org>
Applications have had this power for 7 years, and all that appears to have come from it are rudimentary pickers that mostly don't work smoothly across all browsers and platforms. 

To support this model, users have had to give up permission to all their devices just to use one. This cost/benefit doesn't seem reasonable at face value, and would appear to violate our [priority of constituencies](https://www.w3.org/TR/html-design-principles/#priority-of-constituencies).

But let's be specific: what use case would be hampered by an in-chrome picker? Note that https://github.com/w3c/mediacapture-main/pull/644 does not remove `deviceId`s or the ability to constrain on them. So I don't see the power-loss.

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/652#issuecomment-567271467 using your GitHub account
Received on Thursday, 19 December 2019 00:17:41 UTC

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