Implement clipboardRead/Write content capabilities

extensions/renderer/script_context.cc

Index: extensions/renderer/script_context.cc
diff --git a/extensions/renderer/script_context.cc b/extensions/renderer/script_context.cc
index 6a7629e300b6f88a322651fa459a815c7cae6eac..61c2a12ee59db8285fdab046e1010a3c646be8bc 100644
--- a/extensions/renderer/script_context.cc
+++ b/extensions/renderer/script_context.cc
@@ -17,6 +17,7 @@
 #include "extensions/common/extension_api.h"
 #include "extensions/common/extension_urls.h"
 #include "extensions/common/features/base_feature_provider.h"
+#include "extensions/common/permissions/permissions_data.h"
 #include "gin/per_context_data.h"
 #include "third_party/WebKit/public/web/WebDataSource.h"
 #include "third_party/WebKit/public/web/WebDocument.h"
@@ -273,4 +274,21 @@ gin::ContextHolder* ScriptContext::GetContextHolder() {
   return gin::PerContextData::From(v8_context())->context_holder();
 }
 
+void ScriptContext::SetContentCapabilities(
+    const APIPermissionSet& permissions) {
+  content_capabilities_ = permissions;
+}
+
+bool ScriptContext::HasContentCapability(APIPermission::ID permission) const {
+  if (context_type() != Feature::WEB_PAGE_CONTEXT)
+    return false;

[not at google - send to devlin, 2014/12/10 19:30:07]

You might add a comment like,

Only web page contexts get granted content capabilities. Any other contexts
either have Extensions (and we use that extension's permissions instead) or
WebUI (which has its own brand of superpowers).

at least, that's the comment I'd write, because that's how I write. You probably
write differently.

[Ken Rockot(use gerrit already), 2014/12/10 20:40:25]

Done.

+  if (content_capabilities_.find(permission) != content_capabilities_.end())
+    return true;
+  if (effective_extension_.get()) {
+    return effective_extension_->permissions_data()->HasAPIPermission(
+        permission);
+  }
+  return false;
+}
+
 }  // namespace extensions