Confirmed users
586
edits
QA/Telemetry/Developing a Telemetry Experiment: Difference between revisions
Jump to navigation
Jump to search
QA/Telemetry/Developing a Telemetry Experiment (view source)
Revision as of 19:57, 26 February 2016
, 26 February 2016→Testing everything: Require about:config to flip devtools.chrome.enabled, and disable add-on signature checking
(deploying -m) |
(→Testing everything: Require about:config to flip devtools.chrome.enabled, and disable add-on signature checking) |
||
| Line 53: | Line 53: | ||
** '''experiments.logging.level = 0''', more logging | ** '''experiments.logging.level = 0''', more logging | ||
** '''extensions.logging.enabled = true''', even more logging from the Add-ons Manager | ** '''extensions.logging.enabled = true''', even more logging from the Add-ons Manager | ||
** '''xpinstall.signatures.required = false''', to allow installing unsigned add-ons | |||
Once you enable '''devtools.chrome.enabled''' from about:config, you can paste the rest into the Browser console and be happy: | |||
<code><pre> | <code><pre> | ||
Services.prefs.setBoolPref(" | Services.prefs.setBoolPref("xpinstall.signatures.required", false); | ||
Services.prefs.setBoolPref("toolkit.telemetry.enabled", true); | Services.prefs.setBoolPref("toolkit.telemetry.enabled", true); | ||
Services.prefs.setBoolPref("experiments.logging.enabled", true); | Services.prefs.setBoolPref("experiments.logging.enabled", true); | ||