Disallow user overrides to enterprise policy for plugins.

chrome/browser/resources/plugins.js

Index: chrome/browser/resources/plugins.js
diff --git a/chrome/browser/resources/plugins.js b/chrome/browser/resources/plugins.js
index 05e13897d869701a02cae1e9aa903362641f05a6..b68038d2863d7890634a83af5c96d1181098951d 100644
--- a/chrome/browser/resources/plugins.js
+++ b/chrome/browser/resources/plugins.js
@@ -251,6 +251,17 @@ function isPluginTrusted(plugin) {
 }
 
 /**
+ * @param {Object} plugin An object containing the information about a plugin.
+ *     See returnPluginsData() for the format of this object.
+ * @return {boolean} Whether the plugin is marked click to play by policy.
+ *
+ * This would normally be set by setting the policy DefaultPluginsSetting to 3.
+ */
+function isPluginPolicyClickToPlay(plugin) {
+    return plugin.policy_click_to_play == true;

[Bernhard Bauer, 2016/07/18 21:57:57]

Nit: Really, the == true is a bit overkill if we know (as defined by the Mojo
API) that the field is always going to be a boolean.

[Will Harris, 2016/07/18 22:02:41]

Ack. I was just sticking with the convention in all the other functions.

+}
+
+/**
  * Helper to convert callback-based define() API to a promise-based API.
  * @param {!Array<string>} moduleNames
  * @return {!Promise}