Closed Bug 1468941 Opened Last year Closed Last year

Some of the changes made using CCK2 config (in an old Firefox) are still available after update to the latest Nightly

Categories

(Core :: AutoConfig (Mission Control Desktop), defect)

62 Branch
defect
Not set

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox62 --- affected

People

(Reporter: roxana.leitan, Assigned: mkaply)

References

Details

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0
Build ID: 20180613220131

Affected versions]:
Nightly 62.0a1

[Affected Platforms]:
Windows 10 x64, Mac OS X 10.13

[Preconditions]:
1.Install Firefox ESR 52: http://archive.mozilla.org/pub/firefox/releases/52.0esr/
2.Install CCK2 addon in Firefox ESR 52(downloaded from here:https://mike.kaply.com/cck2/)
3.Customize default search engine(Duck Duck Go), permissions for a website and block private browsing using CCK2 
4.Install an old Firefox build - without autoconfig sandbox(e.g. http://archive.mozilla.org/pub/firefox/nightly/2018/04/2018-04-03-10-01-05-mozilla-central/) and move the customized cck2 file into Firefox Nightly folder
* please make sure that autoconfig.js file contains:
pref("general.config.filename", "cck2.cfg");
pref("general.config.obscure_value", 0);
pref("general.config.sandbox_enabled", true);

[Steps to reproduce]:
1.Launch Firefox with a new profile (old version)
2.Update to the latest Firefox build 

[Expected result]:
The updated Firefox should not contain any changes made using CCK2 file

[Actual result]:
The default search engine is Duck Duck Go and the permission for the website are 
the ones set using CCK2 file, but the private browsing is not blocked anymore

[Note]:
If Firefox (latest build) with CCK2 files is opened with a new profile, the default search engine is Google, the permissions for the website are not customized and the private browsing is not blocked
The CCK2 doesn't remove its settings when uninstalled, so this is working a expected.
Status: NEW → RESOLVED
Closed: Last year
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.