Incorrect browser version detected by websites (Linux)

[Decidedly Devious]

I can't install an add-on because it says I have FF 60 installed and it requires 64+.




But I have FF 65 installed!




Whatismybrowser.com and BrowserSpy both say I have v60 installed.



I suspected a privacy extension was causing it so I disabled them, but nothing changed.
Why are sites misreading the version?

[the-edmeister]

Try resetting the default user agent: https://support.mozilla.org/en-US/kb/ho ... nt-firefox

[therube]

Doesn't ... what was it ... one of those built-in "privacy-like" settings, change the UA to FF 60?
Maybe Content Blocking or was it Private Mode browsing?

Kind of like how all is now "Gecko/20100101".

[therube]

Simple test.

Create a new, clean Profile, then see if your extension will install in there.

[James]

Doesn't ... what was it ... one of those built-in "privacy-like" settings, change the UA to FF 60?
Maybe Content Blocking or was it Private Mode browsing?

Kind of like how all is now "Gecko/20100101".

The privacy.resistFingerprinting preference can set the useragent to show as if you are using current ESR, in this case Firefox 60 ESR.

[therube]

(That was it. Thanks.)

[Decidedly Devious]

First of all, thanks for the replies.

But D.R. was remiss to add Linux to the subject line - this is Mac.


Sorry it's taken so long to respond, I've spent days chasing down another add-on-caused issue.
I discovered that Dark Night Mode was wreaking havoc on Google Images.

I suspected a privacy add-on was causing it that might be related to the issue at the basis of this thread.
It was not.



The browser version issue I started this thread for was caused by two add-ons: Privacy Settings and Chameleon.

I thought I had disabled Chameleon previously in the add-ons window, but now I'm not so sure.
I may have just set it to "Real Profile" and thought that was as good as disabling it.
But there are other settings inside besides merely spoofing the browser profile which apparently remain in effect.

Or I may have disabled each one independently but not simultaneously.
Thus the browser version was still improperly detected because one add-on was still interfering with the website.


In any case, the matter is now resolved and I was able to install the add-on I wanted.