Renderer changes for wiring up shared memory with declarative injection

chrome/browser/extensions/api/declarative_content/content_action.cc

Index: chrome/browser/extensions/api/declarative_content/content_action.cc
diff --git a/chrome/browser/extensions/api/declarative_content/content_action.cc b/chrome/browser/extensions/api/declarative_content/content_action.cc
index 47deb9ea12cbb5d03d14ff15032bf23af74e9ac2..082faa4d4e6d5f4397d99b577f5f0bbeebaefbb4 100644
--- a/chrome/browser/extensions/api/declarative_content/content_action.cc
+++ b/chrome/browser/extensions/api/declarative_content/content_action.cc
@@ -258,7 +258,13 @@ RequestContentScript::RequestContentScript(
 void RequestContentScript::InstructRenderProcessToInject(
     content::WebContents* contents,
     const std::string& extension_id) const {
-  // TODO(markdittmer): Send ExtensionMsg to renderer.
+  contents->GetRenderProcessHost()->Send(

[Devlin, 2014/08/21 17:06:16]

Why not send this to the RenderViewHost so you don't have to look up the tab?

[Mark Dittmer, 2014/08/23 12:21:38]

Done.

+      new ExtensionMsg_ExecuteDeclarativeScript(
+          contents->GetRenderViewHost()->GetRoutingID(),
+          SessionTabHelper::IdForTab(contents),
+          extension_id,
+          script_.id(),
+          contents->GetLastCommittedURL()));
 }
 
 struct ContentActionFactory {