• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Firefox ignores your config settings (Solved)

BarkingGhostar

Diamond Member
OK, so I am on Windows 7 Pro 64-bit running FF43. Yes, I know there is a newer version and I have chosen to not upgrade to the newer version. I have the "Never check for updates (not recommended: security risk)" option checked by deliberate action. So why offer me this option if FF is going to inject a toolbar notification to update?

Why not just remove the "Never check for updates (not recommended: security risk)" feature altogether and stop playing the annoying developer? Anyone else know why this is? And no, I do not wish to update, which is why I enabled the "Never check for updates (not recommended: security risk)" option to begin with.

It reminds me of the Do Not Call and being spammed (ahem, called) by the very same people that brought you the Do not Call. Is this the future of FF? Spam into submission.
 
When I was using an old version, I think this really only ever occurred on Gmail (maybe FF did it so it shows up all the time now). What I did was go into about:config and add a new string called "general.useragent.override" (without quotes) and the value is "Mozilla/5.0 (Windows NT 5.1; rv:48.0) Gecko/20100101 Firefox/48.0"

never saw the nag notification again. You will need to update it after a while again, as the versions go up if you still don't want to upgrade. You'll have to change the rv: value as well as the number at the end.
 
Didn't work. The item that is annoying me is called Firefox/Shield/Heartbeat. I went back into about:config, found the browser.selfsupport.url and per the webpage removed the url to disabled the annoyance. Now testing it.
 
Sorry for the belated reply. Following the directions given on the Firefox/Shield/Heartbeat fixed the issue. No idea how it got initiated to begin with.
 
Back
Top