Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Søg i 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.

Læs mere

Am unable to control "security.sandbox.content.level" using mozilla.cfg on ESR 52.6.0.

more options

Updated to ESR 52.6.0 (On Windows Server 2016 / RDS)

My autoconfig.js file resides in the defaults\prefs folder and contains: // Any comment pref("general.config.filemane", "mozilla.cfg");

My mozilla.cfg file resides in the program folder (c:\program files (x86)\Mozilla Firefox) and contains: // Any comment lockPref("security.sandbox.content.level", 2);

I have tried setting it with just "pref" and "defaultPref" etc.

If I remove the mozilla.cfg file, I get an error that the config file is missing, so I know it is reading it. The problem is no sound can be heard on Mozilla thru an RDS session if the value is set to anything other than "2".

I've tried altering other settings within the mozilla.cfg file and it just appears to be ignoring every setting, period.

Thanks

Updated to ESR 52.6.0 (On Windows Server 2016 / RDS) My autoconfig.js file resides in the defaults\prefs folder and contains: // Any comment pref("general.config.filemane", "mozilla.cfg"); My mozilla.cfg file resides in the program folder (c:\program files (x86)\Mozilla Firefox) and contains: // Any comment lockPref("security.sandbox.content.level", 2); I have tried setting it with just "pref" and "defaultPref" etc. If I remove the mozilla.cfg file, I get an error that the config file is missing, so I know it is reading it. The problem is no sound can be heard on Mozilla thru an RDS session if the value is set to anything other than "2". I've tried altering other settings within the mozilla.cfg file and it just appears to be ignoring every setting, period. Thanks

Valgt løsning

I figured it out. Even though the "2nd" pref line of text in the autoconfig.js file appears to be an "example", if you remove that line, none of your settings will be read/applied. So in essence the following (3) lines of text are required:

// Any comment. You must start the file with a single-line comment! pref("general.config.filename", "mozilla.cfg"); pref("general.config.obscure_value", 0);

Læs dette svar i sammenhæng 👍 0

Alle svar (1)

more options

Valgt løsning

I figured it out. Even though the "2nd" pref line of text in the autoconfig.js file appears to be an "example", if you remove that line, none of your settings will be read/applied. So in essence the following (3) lines of text are required:

// Any comment. You must start the file with a single-line comment! pref("general.config.filename", "mozilla.cfg"); pref("general.config.obscure_value", 0);

Ændret af willfish4fun den