Communicate ExtensionSettings policy to renderers

extensions/common/manifest_constants.cc

Index: extensions/common/manifest_constants.cc
diff --git a/extensions/common/manifest_constants.cc b/extensions/common/manifest_constants.cc
index 8d6be3afc21a672ac34961fc5632c51e42d4c070..f56872902765d8ee2be656a769af2a0f1b39355f 100644
--- a/extensions/common/manifest_constants.cc
+++ b/extensions/common/manifest_constants.cc
@@ -287,6 +287,8 @@ const char kCannotClaimAllURLsInExtent[] =
     "Cannot claim all URLs in an extent.";
 const char kCannotScriptGallery[] =
     "The extensions gallery cannot be scripted.";
+const char kCannotScriptPageByPolicy[] =
+    "This page cannot be scripted due to an ExtensionsSettings policy.";

[asargent_no_longer_on_chrome, 2016/11/23 01:19:23]

In theory, this file should have constants for keys in the manifest and error
messages related to static parsing of extension manifest.json files. It looks
like a few other messages that don't quite fit this criteria have crept in.

Devlin might have a good idea of a better place for it. (These strings are
distinct from user visible messages that get translated, since they are only
reported to extensions in the chrome.runtime.lastError property of API methods
like chrome.tabs.executeScript, etc. that developers can access)

[Devlin, 2016/11/23 17:22:56]

Typically, we just put the errors in the files where they're used (so either the
API implementation or permissions data).

[nrpeter, 2017/01/02 19:57:45]

Done.

 const char kCannotScriptSigninPage[] =
     "The sign-in page cannot be scripted.";
 const char kChromeVersionTooLow[] =