Index: chrome/app/policy/policy_templates.json |
=================================================================== |
--- chrome/app/policy/policy_templates.json (revision 214941) |
+++ chrome/app/policy/policy_templates.json (working copy) |
@@ -112,7 +112,7 @@ |
# 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: 233 |
+# For your editing convenience: highest ID currently used: 234 |
# |
# Placeholders: |
# The following placeholder strings are automatically substituted: |
@@ -2636,6 +2636,25 @@ |
If this policy is not set the default command line will be used.''', |
}, |
+ { |
+ 'name': 'SkipMetadataCheck', |
+ 'type': 'main', |
+ 'schema': { 'type': 'boolean' }, |
+ 'supported_on': ['chrome_frame:30-'], |
+ 'features': { |
+ 'dynamic_refresh': False, |
+ }, |
+ 'example_value': False, |
+ 'id': 234, |
+ 'caption': '''Skip the meta tag check in <ph name="PRODUCT_FRAME_NAME">$3<ex>Google Chrome Frame</ex></ph>''', |
+ 'desc': '''Normally pages with a certain meta tag, for example <meta http-equiv="X-UA-Compatible" content="chrome=1" />, will be rendered in <ph name="PRODUCT_FRAME_NAME">$3<ex>Google Chrome Frame</ex></ph> regardless of the 'ChromeFrameRendererSettings' policy. |
grt (UTC plus 2)
2013/08/02 15:15:00
it looks like the example meta tag you included he
|
+ |
+ If you enable this setting, pages will not be scanned for meta tags. |
+ |
+ If you disable this setting, pages will be scanned for meta tags. |
+ |
+ If this policy is not set, pages will be scanned for meta tags.''' |
+ }, |
], |
}, |
{ |