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

chrome/app/policy/policy_templates.grd

 <?xml version="1.0" encoding="UTF-8"?>
 
 <!-- This file contains definitions of resources that are used in policy
 templates and will be translated for each locale. -->
 
 <grit base_dir="." latest_public_release="0" current_release="1"
       source_lang_id="en" enc_check="möl">
   <outputs>
     <output filename="app/policy/windows/admx/chrome.admx" type="admx" lang="en" />
     <output filename="app/policy/windows/admx/en-US/chrome.adml" type="adml" lang="en" />
@@ skipping 602 matching lines @@
     </message>
     <message name="IDS_POLICY_DEFAULTSEARCHPROVIDERICONURL_DESC" desc="Caption of the 'Icon URL' text field in the 'Default Search Provider' policy settings page.">
       Specifies the favorite icon URL of the default search provider. Optional.
     </message>
     <message name="IDS_POLICY_DEFAULTSEARCHPROVIDERENCODINGS_CAPTION" desc="The label of the 'Encodings' text field in the 'Default Search Provider' policy settings page.">
       Default search provider encodings
     </message>
     <message name="IDS_POLICY_DEFAULTSEARCHPROVIDERENCODINGS_DESC" desc="Caption of the 'Encodings' text field in the 'Default Search Provider' policy settings page.">
       Specifies the character encodings supported by the search provider. Encodings are code page names like UTF-8, GB2312, and ISO-8859-1. They are tried in the order provided. The default is UTF-8.
     </message>
+    <message name="IDS_POLICY_DISABLE3DAPIS_CAPTION" desc="Label of the Disable3DAPIs policy text field.">
+      Disable support for 3D graphics APIs
+    </message>
+    <message name="IDS_POLICY_DISABLE3DAPIS_DESC" desc="Caption of the Disable3DAPIs policy text field.">
+      Disable support for 3D graphics APIs.
+
+      Enabling this setting prevents web pages from accessing the graphics processing unit (GPU). Specifically, web pages can not access the WebGL API and plugins can not use the Pepper 3D API.
+
+      Disabling this setting potentially allows web pages to use the WebGL API and plugins to use the Pepper 3D API. The default settings of the browser may still require command line arguments to be passed in order to use these APIs.
+    </message>
     <!-- Begin Chrome Frame messages -->
     <message name="IDS_POLICY_CHROMEFRAMERENDERERSETTINGS_CAPTION"
              desc="Caption of Chrome Frame renderer policy group">
       Default HTML renderer for <ph name="PRODUCT_FRAME_NAME">$3<ex>Google Chrome Frame</ex></ph>
     </message>
     <message name="IDS_POLICY_CHROMEFRAMERENDERERSETTINGS_DESC"
              desc="Description of the 'Chrome Frame renderer' policy group">
       Allows you to configure the default HTML renderer when <ph name="PRODUCT_FRAME_NAME">$3<ex>Google Chrome Frame</ex>
       </ph> is installed.
       The default setting is to allow the host browser do the rendering, but you
@@ skipping 135 matching lines @@
       Description
     </message>
     <message name="IDS_POLICY_DOC_FEATURE_DYNAMIC_REFRESH"
              desc="The name of the feature that indicates for a given policy that changes to it are respected by Chrome without a browser restart">
       Dynamic Policy Refresh
     </message>
     <!-- End of generated documentation messages  -->
     </messages>
   </release>
 </grit>