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

components/policy/resources/policy_templates.json

 {
 # policy_templates.json - Metafile for policy templates
 #
 # The content of this file is evaluated as a Python expression.
 #
 # This file is used as input to generate the following policy templates:
 # ADM, ADMX+ADML, MCX/plist and html documentation.
 #
 # Policy templates are user interface definitions or documents about the
 # policies that can be used to configure Chrome. Each policy is a name-value
@@ skipping 9579 matching lines @@
       },
       'example_value': [ "xkb:us::en", "xkb:ch::ger" ],
       'max_size': 16777216,
       'id': 365,
       'caption': '''Device sign-in screen keyboard layouts''',
       'tags': [],
       'desc': '''Configures which keyboard layouts are allowed on the <ph name="PRODUCT_OS_NAME">$2<ex>Google Chrome OS</ex></ph> sign-in screen.
 
       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.
     'win_supported_winxpsp2': {
       'desc': '''A label specifying the oldest possible compatible version of Windows. This text will appear right next to a label containing the text 'Supported on:'.''',
       'text': '''Microsoft Windows XP SP2 or later'''
     },
     'mac_chrome_preferences': {
       'desc': '''A text indicating in Mac OS X Workgroup Manager, that currently the preferences of Chromium are being edited''',
       'text': '''<ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> preferences'''
@@ skipping 113 matching lines @@
       'desc': '''Text appended in parentheses next to the policies top-level container to indicate that those policies are of the Recommended level''',
       'text': 'Default Settings (users can override)',
     },
     'doc_complex_policies_on_windows': {
       'desc': '''Text pointing the user to a help article for complex policies on Windows''',
       'text': '''encoded as a JSON string, for details see <ph name="COMPLEX_POLICIES_URL">https://www.chromium.org/administrators/complex-policies-on-windows<ex>https://www.chromium.org/administrators/complex-policies-on-windows</ex></ph>''',
     },
   },
   'placeholders': [],
 }