Since Pale Moon is built upon a Firefox base, it still reports itself to be Firefox to web sites by default. Fortunately, it is trivially simple to turn this off and cause the browser to correctly report itself as PaleMoon.
That's it. Web sites will no longer incorrectly attribute your pageviews to Firefox. If as many people have switched to Pale Moon as have switched to Chrome, the decline in Firefox usage may actually be twice what I originally estimated.
- Create a new tab.
- Type "about:config" into the Address Bar as if it were an internet site (URL).
- Type "compatMode" into the Search box that will appear right below the Address Bar.
- On the line general.useragent.compatMode.firefox there are three settings: user set, boolean, true. Click on "true" and it will change to false.
- Close the tab.
Tuesday, April 8, 2014
Turning Off the Firefox compatMode in Pale Moon
Because the Pale Moon browser is based on Firefox, it reports itself to websites as Firefox. You can turn that off. From Vox Popoli:
Subscribe to:
Post Comments (Atom)
I want to thank all the folks who recommended Pale Moon. I’ve just been FED UP with FF because of the horrific memory leaks, sluggishness, constant pointless UI changes, arrogance of online "help", etc. I've been running v16 forever because whenever I’ve tried to upgrade to newer versions, they’d all pretty much just crash after 30 minutes of heavy use, and not a single version of FF that I’ve ever used has ever fixed the memory leak problems. Not a single one.
ReplyDeleteI actually installed a tiny batch file on quicklaunch so I could quickly kill FF at the point it’s consumed all of my RAM so I could then start over with “Restore Session” to automatically reload all of my previous tabs. After trying every “solution” to the leak problem, that’s the only one that ever did in any good for me. Apparently the arrogant tards at mozilla would rather tweak the UI to death rather than make a browser that actually works. They’re worse than even Microsoft because Microsoft has to listen to their customers sooner or later or go broke. Nonprofits can just drift along forever.
At any rate, I just finished installing PM, including importing everything from FF with their little importer program, and everything went flawlessly, including all settings and the plethora of add-ons I use. The only difficulty was getting roboform attached, which I can’t live without. I did finally dumb around and got the roboform taskbar program to attach roboform to PM, which then worked flawlessly. It is, however, necessary for the roboform taskbar program to run all the time for roboform to continue to work on PM, but this is a very small price to pay to ditch FF forever.
I've used PM for a month now, opening/closing/keeping hundreds of tabs a day, and I’ve been stunned at how much faster PM is than FF, as well as the VERY small memory footprint occupied by PM vs FF. Even after a week's HEAVY usage, PM has not grown beyond 1 GB, and even better, when I close tabs, ALL of the RAM is given back.
Basically, PM is what FF ought to be. Even better, the genius behind Pale Moon, Mark Straver, has committed to keeping the PM UI fundamentally unmolested. I’ll be installing PM instead of FF on all of my client’s computers in the future as well!
(BTW, ALL of the "recommended fixes" for the firefox memory leak problems are a sick joke. Not one of them works. And plugins DO NOT cause the memory leaks! Firefox does! How do I know? Because I switched to Pale Moon, importing everything EXACTLY like it was in Firefox and guess what? No memory leaks in Pale Moon! Oh, and I use Adblock Plus, Flash, Java, DoNotTrackMe, BetterPrivacy CookieCuller, DownloadHelper, Element Hiding Helper, IE View, ViewAbout, Visited, and roboform. So NONE of those is causing the firefox memory leak problems!)