Adding policy support to Chrome Frame's launcher so that additional parameters can be passed to Chr…

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 94 matching lines @@
 #   templates and documentation. The policy definition list that Chrome sees
 #   will include policies marked with 'future'. If a WIP policy isn't meant to
 #   be seen by the policy providers either, the 'supported_on' key should be set
 #   to an empty list.
 #
 # IDs:
 #   Since a Protocol Buffer definition is generated from this file, unique and
 #   persistent IDs for all fields (but not for groups!) are needed. These are
 #   specified by the 'id' keys of each policy. NEVER CHANGE EXISTING IDs,
 #   because doing so would break the deployed wire format!
-#   For your editing convenience: highest ID currently used: 140
+#   For your editing convenience: highest ID currently used: 141
 #
 # Placeholders:
 #   The following placeholder strings are automatically substituted:
 #     $1 -> Google Chrome / Chromium
 #     $2 -> Google Chrome OS / Chromium OS
 #     $3 -> Google Chrome Frame / Chromium Frame
 #     $6 is reserved for doc_writer
 #
 # Device Policy:
 #   An additional flag device_only (optional, defaults to False) indicates
@@ skipping 1662 matching lines @@
           'features': {'dynamic_refresh': False},
           'example_value': ['http://www.example.com', 'http://www.example.edu'],
           'id': 59,
           'caption': '''Always render the following URL patterns in the host browser''',
           'desc': '''Customize the list of URL patterns that should always be rendered by the host browser.
 
           If this policy is not set the default renderer will be used for all sites as specified by the 'ChromeFrameRendererSettings' policy.
 
           For example patterns see http://www.chromium.org/developers/how-tos/chrome-frame-getting-started.''',
         },
+        {
+          'name': 'AdditionalLaunchParameters',
+          'type': 'string',
+          'supported_on': ['chrome_frame:19-'],
+          'features': {'dynamic_refresh': False},
+          'example_value': '--enable-media-stream --enable-media-source',
+          'id': 141,
+          'caption': '''Additional command line parameters for <ph name="PRODUCT_FRAME_NAME">$3<ex>Google Chrome Frame</ex></ph>''',
+          'desc': '''Allows you to specify additional parameters that are used when <ph name="PRODUCT_FRAME_NAME">$3<ex>Google Chrome Frame</ex></ph> launches <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph>.''',

[Mattias Nissler (ping if slow), 2012/03/26 11:04:41]

Please add the additional pro-forma blurb on what happens if the policy is not
specified.

[tommi (sloooow) - chröme, 2012/03/26 11:24:37]

Done.

+        },
       ],
     },
     {
       'name': 'ChromeFrameContentTypes',
       'type': 'group',
       'caption': '''Allow <ph name="PRODUCT_FRAME_NAME">$3<ex>Google Chrome Frame</ex></ph> to handle the following content types.''',
       'desc': '''Allow <ph name="PRODUCT_FRAME_NAME">$3<ex>Google Chrome Frame</ex></ph> to handle the following content types.''',
       'policies': [
         {
           'name': 'ChromeFrameContentTypes',
@@ skipping 875 matching lines @@
       'desc': '''Text appended in parentheses to the policy name to indicate that it has been deprecated''',
       'text': 'deprecated',
     },
     'doc_recommended': {
       'desc': '''Text appended in parentheses next to the policies top-level container to indicate that those policies are of the Recommended level''',
       'text': 'Recommended',
     },
   },
   'placeholders': [],
 }