On Mon, May 14, 2018 at 1:57 PM, Jean-Yves Avenard <jyaven...@mozilla.com> wrote: > Hi > >> On 14 May 2018, at 6:47 pm, Tom Ritter <t...@mozilla.com> wrote: >> >> It seems like this will reveal a lot of information about the user's >> hardware. Does the Resist Fingerprinting preference disable the API or >> report standardized results? If not, can we get that bug on file (and >> if it's easy, point out exactly where we would want to add the 'if() >> return false'?) >> >> -tom > > This is a concern that has been raised previously, and one that you can > ultimately get with existing APIs, but those are typically after the fact, > and by then it’s already too late to allow the user to have a decent media > playback experience > > Existing canPlayType can tell you if we support a particular codec or not.
Okay, it sounds like canPlayType needs to respect Resist Fingerprinting (RFP) as well then. I've filed https://bugzilla.mozilla.org/show_bug.cgi?id=1461454 for this. > During playback, we already expose various metrics (starting from bug > https://bugzilla.mozilla.org/show_bug.cgi?id=580531) this became an official > spec, to determine if the content plays well : number of frames dropped, > number of frames decoded, how many were painted etc... This is the Media Statistics API? We return constant values for this in RFP. > As such MediaCapabilities doesn’t expose much more than what someone can > already gather over time with what’s already existing. > > There are various ways we can build the Media Capabilities answer: collecting > past metrics and build up a dictionary, or make assumptions based on the > decoders (e.g. we know a hardware h264 decoder will always be smooth and > power efficient). > > To get around fingerprinting, at the user’s choice, the obvious work around > would be to report that everything is always supported, will always do so > smoothly with great battery savings. This is something we already do for the > existing apps. The user will end up with a poor video experience however. As > it will typically be served content not always adapted to his machine > capabilities. Right, RFP results in a degraded web experience as it is currently implemented in several areas - our focus so far has been to great as consistent and tight a line as we can, and then investigate how we can improve the experience. -tom _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
