Fx app update deletes customized pref defaults (defaults\pref\all.js)

VERIFIED WONTFIX

Status

()

Toolkit
Application Update
VERIFIED WONTFIX
6 years ago
6 years ago

People

(Reporter: al_9x, Unassigned)

Tracking

Trunk
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
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
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INVALID
(Reporter)

Comment 2

6 years ago
These are not custom prefs, but custom defaults.  Why are they deleted?  An installer update does not delete them.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED
(Reporter)

Comment 4

6 years ago
(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?
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
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
http://mxr.mozilla.org/mozilla1.8.0/source/browser/installer/removed-files.in#10

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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → WONTFIX
(Reporter)

Comment 6

6 years ago
(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.
Status: RESOLVED → UNCONFIRMED
Resolution: WONTFIX → ---
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → WONTFIX
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.