Avatar for Username

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

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

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

  • 1 antwoord
  • 1 het hierdie probleem
  • 1 view
  • Laaste antwoord deur willfish4fun

willfish4fun
willfish4fun
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

Gekose oplossing

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);

Lees dié antwoord in konteks 👍 0

All Replies (1)

willfish4fun
willfish4fun Vraag-eienaar
more options

Gekose oplossing

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);

Gewysig op deur willfish4fun