From: MinxAa <99985274+MinxAa@users.noreply.github.com> Date: Fri, 18 Feb 2022 16:58:28 +0000 (+0100) Subject: Update README.md X-Git-Tag: v3.7~4^2~1 X-Git-Url: https://git.p6c8.net/policy-templates.git/commitdiff_plain/5ba1c0eb58ce648bfa2407085cfe6a2e03ccc930 Update README.md Modified the Preferences `"Status"` values to more clearly reflect that they refer to the various options. Also added a R/W and appearance list. --- diff --git a/README.md b/README.md index d36efa3..21ea6c7 100644 --- a/README.md +++ b/README.md @@ -4334,13 +4334,14 @@ Using the preference as the key, set the `Value` to the corresponding preference `Status` can be "default", "locked", "user" or "clear" -Default preferences can be modified by the user. +* `"default"`: Read/Write: Setting appear as default even if factory default differs. +* `"locked"`: Read-Only: Setting appear as default even if factory default differs. +* `"user"`: Read/Write: Setting appear as changed if it differ from factory default. +* `"clear"`: Read/Write: `Value` has no effect. Resets to factory default on each startup. -If a value is locked, it is also set as the default. +`"user"` preferences persist across invocations of Firefox. It is the equivalent of a user setting the preference. They are most useful when a preference is needed very early in startup so it can't be set as default by policy. An example of this is ```toolkit.legacyUserProfileCustomizations.stylesheets```. -User preferences persist across invocations of Firefox. It is the equivalent of a user setting the preference. They are most useful when a preference is needed very early in startup so it can't be set as default by policy. An example of this is ```toolkit.legacyUserProfileCustomizations.stylesheets```. - -User preferences persist even if the policy is removed, so if you need to remove them, you should use the clear policy. +`"user"` preferences persist even if the policy is removed, so if you need to remove them, you should use the clear policy. See the examples below for more detail.