Adding policy settings for Chrome Frame.

chrome/app/policy/policy_templates.json

Index: chrome/app/policy/policy_templates.json
===================================================================
--- chrome/app/policy/policy_templates.json	(revision 58687)
+++ chrome/app/policy/policy_templates.json	(working copy)
@@ -226,8 +226,27 @@
         'type': 'list',
       }]
     },
+    {
+      'name': 'ChromeFrameRendererSettings',
+      'policies': [ {
+          'name': 'ChromeFrameRendererSettings',
+          'type': 'enum',
+          'items': [
+            {'name': 'RenderInHost', 'value': '0'},
+            {'name': 'RenderInChromeFrame', 'value': '1'},
+          ],
+        }, {
+          'name': 'RenderInChromeFrameList',
+          'type': 'list',
+        }, {
+          'name': 'RenderInHostList',
+          'type': 'list',
+        },
+      ],
+    },

[gfeher, 2010/09/07 16:07:32]

Note that if you put policies into the same group, then its not possible to set
their values to unspecified independently. (In case of ADM/ADMX.) Each of them
will be specified or unspecified at the same time. It's okay if this is what you
want.

[tommi (sloooow) - chröme, 2010/09/07 16:15:58]

In this case, RendererSettings is essentially a switch between these two lists. 
If RendererSettings is 0, then the RenderInChromeFrame list is used for
exclusion, if it is 1, the RenderInHostList is the exclusion list.  So I think
that's what we want.

   ],
   'placeholders': [
+    # Note: keys $1 and $3 are reserved for Chromium and Chromium frame.
     {
       'key': '$2',
       'value': 'http://www.chromium.org/developers/design-documents/network-settings#TOC-Command-line-options-for-proxy-sett'
Property changes on: chrome\app\policy\policy_templates.json
___________________________________________________________________
Added: svn:eol-style
   + LF