Chrome-side of fixes for content-script messaging.

This change adds registration of content scripts, parented to a frame's
context.  When a frame's context goes away, we unregister it and any content
script contexts for it.

There's a corresponding webkit change that lets us know when a content script
context is created.  Filed upstream as
https://bugs.webkit.org/show_bug.cgi?id=27104.

BUG=16228
TEST=install an extension with a content script that communicates with a parent
process.  Messages should be sendable both ways.

Review URL: http://codereview.chromium.org/155309

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@20677 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 8 insertions, 2 deletions

diff --git a/chrome/renderer/extensions/bindings_utils.h b/chrome/renderer/extensions/bindings_utils.h
index 2e8935a5..2c81b0c 100644
--- a/chrome/renderer/extensions/bindings_utils.h
+++ b/chrome/renderer/extensions/bindings_utils.h
@@ -61,9 +61,15 @@ struct ContextInfo {
   v8::Persistent<v8::Context> context;
   std::string extension_id;  // empty if the context is not an extension
 
+  // If this context is a content script, parent will be the frame that it
+  // was injected in.  This is empty if the context is not a content script.
+  v8::Persistent<v8::Context> parent_context;
+
   ContextInfo(v8::Persistent<v8::Context> context,
-              const std::string& extension_id)
-      : context(context), extension_id(extension_id) {}
+              const std::string& extension_id,
+              v8::Persistent<v8::Context> parent_context)
+      : context(context), extension_id(extension_id),
+        parent_context(parent_context) {}
 };
 typedef std::list< linked_ptr<ContextInfo> > ContextList;