Closed Bug 1435277 Opened 8 years ago Closed 7 years ago

Cannot set boolean value using autoconfig scripts

Categories

(Core :: Preferences: Backend, defect)

58 Branch
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: kukuryku19, Unassigned, NeedInfo)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36 Steps to reproduce: 1. Install Firefox 58.0.1 (32 bits) using default settings. Installation directory: C:\Program Files\Mozilla Firefox. 2. Create autoconfig.js file (C:\Program Files\Mozilla Firefox\defaults\pref\autoconfig.js) with following content: // DO NOT REMOVE THIS LINE // Firefox 56+ - enable use of enterprise roots defaultPref("security.enterprise_roots.enabled", true); pref("security.enterprise_roots.enabled", true); 3. Start firefox. 4. Navigate to about:config and accept the risk. 5. Search for security.enterprise_roots Actual results: The value of security.enterprise_roots remains unchanged and is set to false. I've tried with other boolean values and there is the same problem. I am able to change other values (literals, number) as long as script does not change any boolean value. I've also tried using dedicated cfg file with exactly the same results. Expected results: The value of security.enterprise_roots should be: 1) Defaulted to true 2) Changed to true
Component: Untriaged → Preferences
Product: Firefox → Toolkit
Component: Preferences → Preferences: Backend
Product: Toolkit → Core
You are confusing preference files with autoconfig files. If you press Ctrl+Shift+J to open Browser Console, you will see an error like: > C:\Program Files\Mozilla Firefox\defaults\pref\autoconfig.js:4: prefs parse error: unknown keyword Please try: // Firefox 56+ - enable use of enterprise roots pref("security.enterprise_roots.enabled", true); user_pref("security.enterprise_roots.enabled", true);
Flags: needinfo?(kukuryku19)

2019-03-06

This bug is part of a group of bugs which have had an open needinfo for at least 12 weeks.

The request for information has not been answered, and we can't move forward on the bug so we are closing it.

If the defect is still present, please reopen this bug with an updated report.

Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.