- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 27 Mar 2020 17:01:35 +0000
- To: public-webrtc-logs@w3.org
@henbos Specifically on removing required constraints, note that Chrome [today implements](https://jsfiddle.net/jib1/2pnmjz57/) [`info.getCapabilities()`](https://w3c.github.io/mediacapture-main/getusermedia.html#input-specific-device-info) which gives the site capability information about _all_ devices after gUM.
That API exists to allow a site to enforce its constraints while building a picker, or choosing another device outright. [Most sites](https://twitter.com/jibrewery/status/1242512103900094470) enforce some constraints.
That API is also a trove of fingerprinting information.
Luckily, `"user-chooses"` provides feature-parity with this, without the massive information leak:
```js
await getUserMedia({video: constraints, semantics: "user-chooses"});
```
So merging https://github.com/w3c/mediacapture-main/pull/667 would let us retire `info.getCapabilities()` provided we leave constraints alone. 🎉
--
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/669#issuecomment-605114117 using your GitHub account
Received on Friday, 27 March 2020 17:01:42 UTC