Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

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

  • 1 Antwort
  • 1 hat dieses Problem
  • 1 Aufruf
  • Letzte Antwort von 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

Ausgewählte Lösung

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

Diese Antwort im Kontext lesen 👍 0

Alle Antworten (1)

more options

Ausgewählte Lösung

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

Geändert am von willfish4fun