MD Settings: clarify "controlled by" logic

chrome/common/extensions/api/settings_private.idl

Index: chrome/common/extensions/api/settings_private.idl
diff --git a/chrome/common/extensions/api/settings_private.idl b/chrome/common/extensions/api/settings_private.idl
index 904ad39efe26c0ab58a005eac43b87bcbabacd3d..6924488b9eee31315f118b4fe8f93d85a9f56f98 100644
--- a/chrome/common/extensions/api/settings_private.idl
+++ b/chrome/common/extensions/api/settings_private.idl
@@ -14,6 +14,9 @@ namespace settingsPrivate {
     USER_POLICY,
     OWNER,
     PRIMARY_USER,
+    // TODO(dbeam): This is kind of confusing. Extensions can be installed by
+    // users or force installed by a policy (https://goo.gl/f7L5aD). Maybe we
+    // could rename "PolicySource" to "ControlledBy" or "EnforcementSource"?

[stevenjb, 2016/11/09 18:03:30]

First off, I apologize for half completing this and not documenting it well (by
which I mean, at all).

It's been a while since I looked at this, but my head is at least partly in it
since I've been dealing with similar issues for the proxy configuration (which
is its own special hell).

There are a few approaches we could take here. One that comes to mind is to
rename this to EnforcementSource, rename PolicyEnforcement to EnforcementType
and include { POLICY_ENFORCED, POLICY_RECOMMENDED, EXTENSION_ENFORCED, NONE }.

Let's chat Wed and maybe put together a quick design / brainstorming doc.

     EXTENSION
   };