Skip to content

Add general pref guidance #649

@jaredlockhart

Description

@jaredlockhart

Let's add this on the desktop Feature configuration docs as general guidance for using prefs:

  1. Avoid using a pref in the first place and read directly from Nimbus API variables when possible.
  2. If you must use a pref, there should be no more than 1 writer per 1 pref (ie code, remote setting, manual interaction in about:config). If a pref must be written to by multiple writers, consider using multiple prefs instead to maintain the 1 pref : 1 writer relationship.
  3. Avoid guiding users to manually interact with and set prefs in about:config. This can weaken security practices by normalizing users to interact with complex 'under the hood' settings which can be taken advantage of by malicious actors. In addition, manually interacting with prefs that are managed by code can create confusing situations for users where their changes are overwritten or reverted.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions