The buildID changing rapidly provides a bigger, rather than a smaller,
fingerprinting surface.
~ Gijs
On 01/11/2016 08:09, Chris Pearce wrote:
It's not just Netflix that the media playback team has used
navigator.buildID in order to validate fixes; we've used it with other
large video sites too. It's invaluable for determining whether a bug has
been fixed in a build. Can we only disable navigator.buildID in release
builds? Don't users on pre-release versions of Firefox update more
often, and thus the buildID changes too rapidly to be useful?
cpearce.
On 11/1/2016 7:01 AM, Domenic Denicola wrote:
On Monday, October 31, 2016 at 10:54:11 AM UTC-4, Mike Taylor wrote:
On 10/31/16 9:16 AM, Henri Sivonen wrote:
On Oct 31, 2016 16:02, "Mike Taylor" <mi...@mozilla.com
<mailto:mi...@mozilla.com>> wrote:
On 10/29/16 9:21 AM, Kohei Yoshino wrote:
I think now is a good time to think about navigator.buildID again
Thoughts?
Seems like we'd potentially end up breaking legacy sites that sniff
that to mean "isMozilla".
I suggest returning a constant value to general Web sites to avoid this
problem.
I think that's a good path forward.
--
Mike Taylor
Web Compat, Mozilla
If Gecko has no plans to remove this and conform to the spec, could
someone file an issue or pull request on
https://github.com/whatwg/html requesting that buildID be added to
Gecko compatibility mode?
https://html.spec.whatwg.org/multipage/#concept-navigator-compatibility-mode
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
