Added group policy for disabling all client-side 3D APIs in Chromium ...

chrome/app/policy/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 488 matching lines @@
           'type': 'list',
           'supported_on': ['chrome.*:8-'],
           'annotations': {
             'features': {'dynamic_refresh': 1},
             'example_value': ['UTF-8', 'UTF-16', 'GB2312', 'ISO-8859-1']
           }
         },
       ]
     },
     {
+      'name': 'Disable3DAPIs',
+      'type': 'main',
+      'supported_on': ['chrome.*:9-'],
+      'annotations': {
+        # It'll be difficult to support dynamically disabling access to these APIs.
+        'features': {'dynamic_refresh': 0},
+        'example_value': False,
+      }
+    },
+    {
       'name': 'ChromeFrameRendererSettings',
       'type': 'group',
       'policies': [{
         'name': 'ChromeFrameRendererSettings',
         'type': 'enum',
         'items': [
             {'name': 'RenderInHost', 'value': '0'},
             {'name': 'RenderInChromeFrame', 'value': '1'},
         ],
         'supported_on': ['chrome_frame:8-'],
@@ skipping 52 matching lines @@
     {
       'key': '$4',
       'value': 'http://www.chromium.org/developers/how-tos/chrome-frame-getting-started'
     },
     {
       'key': '$5',
       'value': 'http://www.chromium.org/administrators/policy-templates'
     },
   ]
 }