Communicate ExtensionSettings policy to renderers

chrome/test/data/extensions/api_test/content_scripts/policy_blocked/background.js

Index: chrome/test/data/extensions/api_test/content_scripts/policy_blocked/background.js
diff --git a/chrome/test/data/extensions/api_test/content_scripts/policy_blocked/background.js b/chrome/test/data/extensions/api_test/content_scripts/policy_blocked/background.js
new file mode 100644
index 0000000000000000000000000000000000000000..3b6c00c34fb5c6a7cb7f7422e4f6f9f87937fc7c
--- /dev/null
+++ b/chrome/test/data/extensions/api_test/content_scripts/policy_blocked/background.js
@@ -0,0 +1,8 @@
+// Copyright (c) 2016 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+// Give 2 seconds to inject JS, if no response hasn't injected

[Devlin, 2017/02/14 23:17:10]

This is inherently flaky - there is no guarantee that js will have injected in 2
seconds.

Instead, we should cause a visible change to the page (e.g. setting a variable
on window, modifying the title, etc), wait for a deterministic point after which
we know the content script would have injected, and then check it.

[nrpeter, 2017/03/22 23:47:39]

This case is already tested under a different test, removed it.

+setTimeout(function() {
+  chrome.test.notifyPass();
+}, 2000);

[Devlin, 2017/02/14 23:17:10]

<random comment spot because I can't comment in inject.html> looks like
inject.html is empty?

[nrpeter, 2017/03/22 23:47:39]

Yes, I just needed a valid page to browse to so code could be injected. This
test was removed however.