Our currentDepending on user-agent string does not include the word "Firefox".string, This can result insome web browsing failures on websites that persist in usingto load due to use of UA sniffing (rather than, say, feature detection or defensive programming). Shall we:
1. Keep defacto policy. Drop "Firefox",feature detection or defensive programming).
User-agent is a string of this form: `Mozilla/[version] ([system and browser information]) [platform] ([platform add "PureBrowser".
* Plain: Include Use IceWeasel-style policy.`PureBrowser` in extensions
* Compatibility mode: Include `Firefox` and `PureBrowser` Keep "Firefox",in extensions
* Impersonation: Include `Firefox` add "PureBrowser".
* Subtle: Include `PureBrowser in browser information, Use IceCat- and Tor-style policy.and `Firefox` in extensions
Plain is the default when Firefox is built with "Brand" changed Keep "Firefox",to "PureBrowser".
Compatibility mode is the style when a rebranded Firefox do not add "PureBrowser".
4. Something else / additional details?
* Examples of failures include:
* AMO, wide reach, impacts access to arbitrary add-ons. Even IceCat supports AMO access (they just don't promote it)is runtime-configured with `general.useragent.compatMode.firefox` enabled.
This has been applied to PureBrowser since 52.9.0esr-1pureos2.
Impersonation is practiced e.g. by GNU IceCat fork of Firefox (see https://tracker.pureos.net/T202
* Jitsi Meet, lower reach, impacts access but they are willing to accept a patch.net/w/troubleshooting/firefox_compat_mode/).
Subtle is suggested by Mozilla as acceptable for AMO (see https://tracker.pureos.net/T201T595#11999).
Examples of failures include AMO (see T202) and Jitsi Meet (see T201).
* An idiosyncratic UA string has privacy implications (see https://panopticlick.eff.org -- there are many other tracking signals, but any idiosyncrasy has an impact)
* This would suggest opimpersonation 3mode is preferable.
* We don't want to commit to "keep Panopticlick score as low as possible", Tor is better suited to that use case. This change should not be read as implying that.
* What are the benefits of an idiosyncratic UA? Measuring browser reach globally. Measuring browser reach on our own sites. What value does this have? Any other benefits? If there is value here, we could take the IceWeasel approach.
* Global scale trackers may count us as Firefox if we include "Firefox" in the UA string. Is this good or bad?