Plugin Power Saver: Implement option in Settings.

components/policy/resources/policy_templates.json

Index: components/policy/resources/policy_templates.json
diff --git a/components/policy/resources/policy_templates.json b/components/policy/resources/policy_templates.json
index 2a1a3d45f0b034b7ee83d818a01a8cf02c0b1f49..9fd77b938449e2faa4036c035132b32e1688e0a3 100644
--- a/components/policy/resources/policy_templates.json
+++ b/components/policy/resources/policy_templates.json
@@ -2491,7 +2491,7 @@
           'type': 'int-enum',
           'schema': {
             'type': 'integer',
-            'enum': [ 1, 2, 3 ],
+            'enum': [ 1, 2, 3, 5 ],
           },
           'items': [
             {
@@ -2509,6 +2509,11 @@
               'value': 3,
               'caption': '''Click to play''',
             },
+            {
+              'name': 'DetectImportantContent',
+              'value': 5,

[Andrew T Wilson (Slow), 2014/12/16 09:48:09]

Why is this 5 and not 4?

I would just not add this as a policy setting for now (it isn't likely that any
enterprise will want to enforce "DetectImportantContent" via policy).

So I'd say to revert the changes to this file, and just make sure that
ClickToPlay policy is treated the same as "Right click to play" in settings
(i.e. make sure that you can still right click to play content when this policy
is set).

[tommycli, 2014/12/16 19:55:47]

Done. I reverted this. It was '5' because it's an enum, and '4' was used for
"Allow cookies for Session only"

+              'caption': '''Detect important content''',
+            },
           ],
           'supported_on': ['chrome.*:10-', 'chrome_os:11-'],
           'features': {