From a9a69dcfcbe41513b4aa21507a89ebfb7982ee63 Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Tue, 5 Jan 2021 16:53:31 -0500 Subject: [PATCH] Updated Deploying uBlock Origin (markdown) --- Deploying-uBlock-Origin.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Deploying-uBlock-Origin.md b/Deploying-uBlock-Origin.md index 2ff3a1c..eb1b29d 100644 --- a/Deploying-uBlock-Origin.md +++ b/Deploying-uBlock-Origin.md @@ -7,6 +7,8 @@ I do not know much about that administrator stuff, so I will let a knowledgeable Administrators can force specific configurations to deployed uBlock Origin ("uBO"). At launch time, uBO will look for a setting named `adminSettings`, and if it exists, it will parse, extract and overwrite a user's settings with the administrator-assigned ones. +New standalone settings are being added as per demand, see ["Deploying uBlock Origin: configuration"](https://github.com/uBlockOrigin/uBlock-issues/wiki/Deploying-uBlock-Origin:-configuration). + For **Firefox**, refer to Mozilla documentation about ["Native manifests"](https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Native_manifests) (sections about ["Managed storage manifests"](https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Native_manifests#Managed_storage_manifests) and [its location](https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Native_manifests#Manifest_location)). You can also consult [this specific comment](https://github.com/gorhill/uBlock/issues/2986#issuecomment-364035002) in uBO issue tracker. For **Firefox-legacy**, the `adminSettings` entry must be added to `about:config`, the key name is `extensions.ublock0.adminSettings`, and the value is a plain string -- which must be JSON-parseable.