W3C home > Mailing lists > Public > public-webrtc@w3.org > March 2020

[mediacapture-main] Deprecate inputDeviceInfo.getCapabilities() for better privacy (#672)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Fri, 27 Mar 2020 22:02:36 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-589434844-1585346555-sysbot+gh@w3.org>
jan-ivar has just created a new issue for https://github.com/w3c/mediacapture-main:

== Deprecate inputDeviceInfo.getCapabilities() for better privacy ==
From https://github.com/w3c/mediacapture-main/issues/669#issuecomment-605114117:
> @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. 🎉

So far, it looks like only Chrome/Edge implement it ([WPT](https://wpt.fyi/results/mediacapture-streams/MediaStreamTrack-getCapabilities.https.html?label=experimental&label=master&aligned))

Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/672 using your GitHub account
Received on Friday, 27 March 2020 22:02:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 27 March 2020 22:02:40 UTC