Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

mozilla.cfg doesn't work version 48

more options

Using the following doesn't do anything to the about:config settings in firefox:

mozilla.cfg with just the following:

// lockPref("app.update.enabled", false);

This doesn't change the setting from true to false or dither it out as locked? Does this method not work for version 48?

I do have the local-settings.js file with the following under defaults/pref:

// pref("general.config.filename", "mozilla.cfg"); pref("general.config.obscure_value", 0);

Help!!!

Using the following doesn't do anything to the about:config settings in firefox: mozilla.cfg with just the following: // lockPref("app.update.enabled", false); This doesn't change the setting from true to false or dither it out as locked? Does this method not work for version 48? I do have the local-settings.js file with the following under defaults/pref: // pref("general.config.filename", "mozilla.cfg"); pref("general.config.obscure_value", 0); Help!!!

Asịsa ahọpụtara

I can't believe it, the problem was I needed to be using a single ' in the js file not regular double quotes " that I see on just about everything I have searched on. Arrrgh, very frustrating. It works now.  :-)

Gụọ azịza a na nghọta 👍 1

All Replies (5)

more options

Have you always had the // at the beginning of those lines? In JavaScript, that would turn the line from a command into a comment, which should deactivate it. ??

more options

Everything I have read says to comment out the first line of the file...is that not correct?

more options

// is on its own line but the formatting in the question changed it to the same line.

more options

Oh, okay.

I'm still on Firefox 47 and haven't heard about any changes related to autoconfig in Firefox 48, so hopefully someone else knows what's going on.

more options

Asịsa Ahọpụtara

I can't believe it, the problem was I needed to be using a single ' in the js file not regular double quotes " that I see on just about everything I have searched on. Arrrgh, very frustrating. It works now.  :-)