In the next version (probably v6.0) I will move towards a more webExtension-ish approach (which means the settings dialog will be converted to HTML).
During this refactoring (see WebExt branch) I also stop using the LegacyPrefs API. Most options have been moved/migrated towards local storage already, but we still allow a manual override for defaultImport and templateFolder which is currently pulled from the legacy prefs tree (about:config). This will be replaced by managed local storage. Here is a quick overview:
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/storage/managed
So system admins no longer have to set these prefs, but have to save the data in a json file.
@SamuelPlentz
In the next version (probably v6.0) I will move towards a more webExtension-ish approach (which means the settings dialog will be converted to HTML).
During this refactoring (see WebExt branch) I also stop using the LegacyPrefs API. Most options have been moved/migrated towards local storage already, but we still allow a manual override for
defaultImport
andtemplateFolder
which is currently pulled from the legacy prefs tree (about:config). This will be replaced by managed local storage. Here is a quick overview: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/storage/managedSo system admins no longer have to set these prefs, but have to save the data in a json file.
System admins used different means to manipulate the prefs to provision the config to their clients and they can use similar means to provision the json file to all their clients. This document covers where that json file is located: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Native_manifests#manifest_location
Would you have time to update our documentation?