forked from mirrors/gecko-dev
03ff66c89d
There are some complications here to handle unpackaged and packaged builds. In addition, there could be a difference between App prefs and GRE prefs. Since the underlying backgroundtasks code is built as part of Gecko (i.e., `toolkit/...` rather than `browser/...`) I have favoured GRE prefs. I think, however, that what is written will work for App-specific prefs, but I'm not concerned with that detail at this time. This also add tests for backgroundtask-specific prefs, which are structured as both xpcshell and mochitest-chrome tests because locally, the former tests unpackaged builds and the latter can accommodate testing packaged builds. We could use mochitest-chrome for both, but this has been pleasant to work with locally. Differential Revision: https://phabricator.services.mozilla.com/D97510
27 lines
1.2 KiB
JavaScript
27 lines
1.2 KiB
JavaScript
/* This Source Code Form is subject to the terms of the Mozilla Public
|
|
* License, v. 2.0. If a copy of the MPL was not distributed with this
|
|
* file, You can obtain one at http://mozilla.org/MPL/2.0/. */
|
|
|
|
pref("browser.dom.window.dump.enabled", true);
|
|
pref("devtools.console.stdout.chrome", true);
|
|
|
|
pref("network.process.enabled", false);
|
|
|
|
pref("toolkit.telemetry.archive.enabled", false);
|
|
pref("toolkit.telemetry.firstShutdownPing.enabled", false);
|
|
pref("toolkit.telemetry.healthping.enabled", false);
|
|
pref("toolkit.telemetry.newProfilePing.enabled", false);
|
|
pref("toolkit.telemetry.eventping.enabled", false);
|
|
pref("toolkit.telemetry.ecosystemtelemetry.enabled", false);
|
|
pref("toolkit.telemetry.prioping.enabled", false);
|
|
pref("datareporting.policy.dataSubmissionEnabled", false);
|
|
pref("datareporting.healthreport.uploadEnabled", false);
|
|
|
|
pref("browser.cache.offline.enable", false);
|
|
pref("browser.cache.offline.storage.enable", false);
|
|
pref("browser.cache.disk.enable", false);
|
|
pref("permissions.memory_only", true);
|
|
|
|
// For testing only: used to test that backgroundtask-specific prefs are
|
|
// processed. This just needs to be an unusual integer in the range 0..127.
|
|
pref("test.backgroundtask_specific_pref.exitCode", 79);
|