The default bug view has changed. See this FAQ.

Autoconfig defaults/preferences not working

RESOLVED WONTFIX

Status

()

Core
Preferences: Backend
RESOLVED WONTFIX
4 years ago
4 years ago

People

(Reporter: Dimas, Unassigned)

Tracking

21 Branch
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(firefox-esr17 unaffected)

Details

(Reporter)

Description

4 years ago
Before Firefox 14 we can put our local preference file (eg local-settings.js) inside the defaults/pref directory.

Since 14 we have to put them in defaults/preferences directory as said in bug 779437 (https://bugzilla.mozilla.org/show_bug.cgi?id=779437#c4).

Now, with Firefox 21, it seems that the defaults/preferences directory isn't read, but putting the js file in defaults/pref works.

Somebody can explain or confirm this is a bug?

Thanks

Updated

4 years ago
Component: Preferences → Preferences: Backend
Product: Firefox → Core

Updated

4 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 1

4 years ago
I don't think that this is a critical bug. There is an easy workaround but is disruptive to workflow, so should probably be major. Can we change this?
Flags: needinfo?(dimas.sc)

Comment 2

4 years ago
Can you identify the regressing changeset using http://mozilla.github.io/mozregression/? That'll ensure speedy resolution.
tracking-firefox-esr17: --- → ?
(Reporter)

Comment 3

4 years ago
(In reply to Thomas [:Tad] from comment #1)
> I don't think that this is a critical bug. There is an easy workaround but
> is disruptive to workflow, so should probably be major. Can we change this?

I can only explain my reasons but feel free to change it. The workaround is easy for a single computer, not for Firefox installations distributed through hundreds of PCs. If this can't be fixed in Firefox 21 we won't update to the new version. I marked it as a critical because other people in the same situation can be in trouble if they update without knowing about this bug.
Flags: needinfo?(dimas.sc)

Comment 4

4 years ago
The tool for identifying the regression doesn't work:

"Mozilla tools directory: C:\mozilla-build\"
hartnegg@TEST-VBOX ~
$ easy_install mozregression
hartnegg@TEST-VBOX ~
$ mozregression --good=2013-03-16
bash: mozregression: command not found
hartnegg@TEST-VBOX ~
$ moznightly --date=2013-03-23
bash: moznightly: command not found

Comment 5

4 years ago
The bug was already present in a very early version:
pub/mozilla.org/firefox/nightly/2013/02/2013-02-28-04-20-12-mozilla-aurora/firefox-21.0a2.en-US.win32.installer.exe

And in this earlier version
pub/mozilla.org/firefox/nightly/2013/02/2013-02-20-04-20-17-mozilla-aurora/firefox-21.0a2.en-US.win32.installer.exe
it doesn't even work in pref directory, there it reports "failed to read to configuration file".

Comment 6

4 years ago
I found even older versions named
mozilla-central\firefox-21.0a1.en-US.win32.installer.exe
and nailed it down here:
2013-02-11 ok
2013-02-12 broken

Comment 7

4 years ago
This is a mess. Several changes at different times, all of them errors.

First preferences stopped working and prefs started giving errors regarding mozilla.cfg. This happened between 2013-02-11 and 2013-02-12.

Then pref was also ignored, this happened between 2013-02-27 and 2013-02-28. Probably somebody wanted to fix the mozilla.cfg thing, but effectively breaking it even more.

Then at some later time pref must have been restored and made accept mozilla.cfg again, but preferences remained inactive. This is the current state. I won't hunt down the date when this happened.

Comment 8

4 years ago
The issue is that everything moved under the browser directory now because of metro.

Everything shoudl go in:

browser\default\preferences

I'll post something.

I don't necessarily like the change, but it's the right thing to do based on the changes to the Firefox directories.

Comment 9

4 years ago
Relevant bugs:

https://bugzilla.mozilla.org/show_bug.cgi?id=841011
https://bugzilla.mozilla.org/show_bug.cgi?id=861775
Severity: critical → normal
(Reporter)

Comment 10

4 years ago
Regressing changeset: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=5835bc763be7&tochange=36525224b14e
(Reporter)

Comment 11

4 years ago
Thanks Michael. I've some questions...

- If Firefox <21 only read /defaults and Firefox >=21 only read browser/defaults how can the domain administrators manage this change? It is impossible to update hundreds of PCs at the same time to Firefox 21. The only way is duplicating /defaults content?

- Where is the official documentation about Autoconfig? Is it updated? How we can stay tunned about these important changes?

- Moving all the /defaults subdirectories to /browser/defaults is ok? Are there more directories affected? /searchplugins, /extensions, /distribution, ... ?

Thx
I got the other bug wrong:

https://bugzilla.mozilla.org/show_bug.cgi?id=842334

And yes,everything needs to be in the browser directory now.

There is no official documentation about autoconfig. I'll be posting about this soon.

As far as duplicating content goes, you could certainly create a browser directory on Firefox 20 and duplicate the preferences. They wouldn't be read until Firefox 21 came out (just make sure FF 21 didn't overwrite those files).

Comment 13

4 years ago
Confirmed, it works with autoconfig.js in browser\defaults\preferences\
(not default, must be defaults, the s is important).

The file mozilla.cfg must still be in %ProgramFiles%\Mozilla Firefox

Btw. the directory defaults/profile has also moved to browser, but defs stays in its old place.

Hint: the installer creates the directory 'browser', so a config script can use the presence of this directory to differentiate between old and new method. The installer still does not create the directory 'defaults' though.

Btw. why must all non-metro stuff move to directory browser? Is metro-firefox not also a browser?
> Btw. why must all non-metro stuff move to directory browser? Is metro-firefox not also a browser?

It's part of a larger move to separate the Gecko Runtime Engine.

See:

https://bugzilla.mozilla.org/show_bug.cgi?id=755724
Does this just need the patch in bug 841011 to be uplifted to ESR17?
(In reply to lsblakk@mozilla.com from comment #15)
> Does this just need the patch in bug 841011 to be uplifted to ESR17?

This problem is FF 21 only, so there is no uplift.

I'm going to close this bug as WONTFIX. The move to browser is annoying, but folks will just have to deal with it.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
status-firefox-esr17: --- → unaffected
tracking-firefox-esr17: ? → ---
You need to log in before you can comment on or make changes to this bug.