If _mozAddonManager is present for you (boolean, false or true) then you might find interest in: If privacy.resistFingerprinting is true with Waterfox 56.2.0 then a pretence of Firefox 60 will not apply during normal browsing, AMO will behave as if Waterfox is Firefox ESR 52.0. Fingerprint resistance – privacy.resistFingerprintingĪbout:config?filter=privacy.resistFingerprinting
WATERFOX REVIEW 2017 INSTALL
The pretence of Firefox 60 with Waterfox 56.2.0 can be troublesome for people who might install things whilst seeking or browsing extensions at Add-ons for Firefox – (AMO). This would still be better tan "Firefox 56.2" I suppose, and would actually fix the "outdated" messages. to the developers and providers of the service, for considerate action and observations.įrom post-closure discussion in the area:.to for taking the initiative in this case.Please move the discussion (to) the Waterfox github page. The question is if it will get the features of newer firefox versions. I cannnot recommend Waterfox for users if it will be stuck at the base of firefox 56 forever since sites may require newer technologies.I think blacklisting will not occure that often! You will be backwards compatible by default but it will make it possible for services as this to whitelist the browser. Only then you may even think to "lie" about the firefox version. And this is how hundreds of other browsers forked from chrome or firefox or webkit do it. This makes it easier to detect the browser. You can keep the Firefox part but add your own string. Please add a an explicit name of the browser to the user agent string.I now whitelisted Waterfox by looking for "Firefox 56.2" in the user agent string. This extension combination should make it possible to use the Waterfox user agent string for most sites, and the Firefox (or other) UA string for sites that specifically require that.īrowser-update/browser-update issue 397 is closed, with this comment: The usual combo is and, but typically not, and certainly not That should show the list of script-hosting domains, but not all domains are required to be added with most sites, as many are simply domains used for ads and tracking. To find out, which domains a site requires for functioning, use the User Agent Switcher for global UA switching with the default Firefox UA, and NoScript.
Note also, that it's not just the main domain, but some of the additional domains hosting scripts, too. Site-specific user-agent strings are possible on desktop Firefox and derivatives, after all, since I now finally got the right extension combination:īut both have to be installed, or it won't work. Personally I admit a conflict between the privacy advantage of having Waterfox removed from the UA and the pleasure of knowing that I am identified as a Waterfox fan. Mozilla/5.0 (Windows NT 6.1 Win64 圆4 rv:55.0) Gecko/20100101 Firefox/55.0.2Ī bit cumbersome maybe, and requires modifying the value when Waterfox is updated, but it works. If I then check my User Agent on a site such as I'll notice: Set to the browser's User Agent with Waterfox removed.Īll we have to do is modify (create if editing the about:config) a hidden setting called and give it the same value as that of .com (to make it easy and faultless). It is possible to override the User Agent on Waterfox 52.0.2 at least, which I am using.
0 kommentar(er)
