1. unpack a non current nightly zip
2. add a defaults\pref\all.js
3. perform a help->about update
4. all.js gets deleted
custom prefs can be placed in /path/to/firefox/defaults/profile/user.js
These are not custom prefs, but custom defaults. Why are they deleted? An installer update does not delete them.
Installing on top of with the installer should delete them which I'll verify when I have a chance.
Custom preferences should be in a file that is not one of the Firefox prefs files under defaults\pref\.
The reason it is deleted is because this Firefox prefs file has been moved into the omni.jar file. Also, the old file contains values that have been changed and some of the changes will cause breakage.
Leaving open to verify that the installer does delete all.js, etc.
(In reply to Robert Strong [:rstrong] (do not email) from comment #3)
> Custom preferences should be in a file that is not one of the Firefox prefs
> files under defaults\pref\.
all.js does not appear to be a firefox installed file, it is neither in defaults\pref\ nor in omni.jar, so why again are you deleting a user supplied defaults file?
Sorry about accidentally resolving it fixed.
Just had a chance to look into this and all.js was removed during an update as far back as Firefox 1.5
To prevent this from happening you will need to use a pref file name that has never been used by Firefox. A safe bet would be to prefix the file name with an _.
We aren't going to change Firefox so this file isn't deleted so wontfixing.
(In reply to Robert Strong [:rstrong] (do not email) from comment #5)
> We aren't going to change Firefox so this file isn't deleted so wontfixing.
Deleting a user supplied defaults file is incorrect behavior, not saying this is a high priority, but WONTFIX is inappropriate, confirm it and leave it open.
No, it isn't considered a user supplied defaults pref file because the all.js pref file used to exist in Firefox. This is why it is deleted it on update. Any pref file name that has ever existed is not considered supported. We are not going to change that policy and we aren't going to fix this bug so please don't reopen.