DevTools: disable the Chrome tab debugging warning for force-installed extensions.

components/policy/resources/policy_templates.json

Index: components/policy/resources/policy_templates.json
diff --git a/components/policy/resources/policy_templates.json b/components/policy/resources/policy_templates.json
index 0b1c89b145dd905c3d744de03b2b03d6223861d6..479f762d903a84f80ac7b015ed74f8a514184a8f 100644
--- a/components/policy/resources/policy_templates.json
+++ b/components/policy/resources/policy_templates.json
@@ -9597,6 +9597,23 @@
 
       If this policy is set to a list of input method identifiers, the given input methods will be available on the sign-in screen. The first given input method will be preselected. While a user pod is focused on the sign-in screen, the user's least recently used input method will be available in addition to the input methods given by this policy.  If this policy is not set, the input methods on the sign-in screen will be derived from the locale in which the sign-in screen is displayed.  Values which are not valid input method identifiers will be ignored.''',
     },
+    {
+      'name': 'DeveloperToolsSilentManagedDebuggerAPIEnabled',

[Thiemo Nagel, 2017/02/22 11:13:29]

Nit: Imho the "Managed" part of the name is hard to parse since it doesn't refer
to any of the terms in the name.  (Iiuc it refers to "managed extension" which
however is not part of the name.)  I'd suggest to drop it:
DeveloperToolsSilentDebuggerAPIEnabled would seem more lucid to me.

[pfeldman, 2017/02/22 16:40:46]

There is also--silent-debugger-extension-api command line flag and it might be
confusing why those two are not wired together should we drop the Managed. The
difference is that the policy applies to forced / policy-installed extensions
only. I'm thinking that it might be Ok to have a non-readable name that forces
investigation upon stumbling upon when making a change.

+      'type': 'main',
+      'schema': { 'type': 'boolean' },
+      'supported_on': ['chrome.*:58-', 'chrome_os:58-'],
+      'features': {
+        'dynamic_refresh': True,
+        'per_profile': True,
+      },
+      'example_value': False,
+      'id': 366,
+      'caption': '''Enable Developer Tools silent chrome.debugger extensions API for managed extensions''',

[Thiemo Nagel, 2017/02/22 11:13:29]

Nit: Please tag "chrome.debugger" as non-translatable (cf. instructions at the
top of the file).

Nit: Instead of "managed extension" I think a more common term is
"force-installed".

[pfeldman, 2017/02/22 16:40:46]

Done.

+      'tags': [],

[Thiemo Nagel, 2017/02/22 11:13:29]

Nit: "system-security" would seem appropriate here

[pfeldman, 2017/02/22 16:40:45]

Done.

+      'desc': '''Enables enterprise-managed extensions to instrument browser without the user-visible warning.

[Thiemo Nagel, 2017/02/22 11:13:29]

Nit: instrument *the* browser

[pfeldman, 2017/02/22 16:40:45]

Done.

+
+      If you enable this setting, enterprise-managed browser extensions will be able to attach to the browser and instrument it without the user-visible warning.'''

[Thiemo Nagel, 2017/02/22 11:13:29]

Nit: It's preferred to not address the audience directly ("you") and rather use
passive voice.

Nit: the user-visible warning --> *a* user-visible warning

[pfeldman, 2017/02/22 16:40:46]

Done, but this file has 134 "If you" mentions.
Done.

[Thiemo Nagel, 2017/02/22 17:15:10]

I'm not surprised.  We have to start somewhere, I guess though.

+    },

[Thiemo Nagel, 2017/02/22 11:13:29]

Nit: Please explicitly spell out what happens when the policy is disabled or
unset.

[pfeldman, 2017/02/22 16:40:46]

Done.

   ],
   'messages': {
     # Messages that are not associated to any policies.