Index: chrome/app/policy/policy_templates.json |
diff --git a/chrome/app/policy/policy_templates.json b/chrome/app/policy/policy_templates.json |
index 19fb062b5cc61acb1147412df35881620e0590b6..5eb96e61e7eed243ef9907388fa73860f1ee6040 100644 |
--- a/chrome/app/policy/policy_templates.json |
+++ b/chrome/app/policy/policy_templates.json |
@@ -103,7 +103,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: 114 |
+# For your editing convenience: highest ID currently used: 115 |
# |
# Placeholders: |
# The following placeholder strings are automatically substituted: |
@@ -2223,6 +2223,19 @@ |
This setting is used to enable the TLS origin-bound certificates extension for testing. This experimental setting will be removed in the future.''', |
}, |
+ { |
+ 'name': 'EnableMemoryInfo', |
+ 'type': 'main', |
+ 'supported_on': ['chrome.*:16-'], |
+ 'features': {'dynamic_refresh': True}, |
+ 'future': True, |
Mattias Nissler (ping if slow)
2011/12/12 10:10:58
Is this going to stay for good? If yes, you can ju
|
+ 'example_value': False, |
+ 'id': 115, |
+ 'caption': '''Enable reporting memory info (JS heap size) to page''', |
+ 'desc': '''Allows pages to access JavaScript memory usage statistics. |
+ |
+ This settings makes the memory statistics from the Developer Tools Profiles panel available to the web page itself.''', |
+ }, |
], |
'messages': { |
# Messages that are not associated to any policies. |