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, 6 insertions, 2 deletions

diff --git a/webkit/glue/webview_delegate.h b/webkit/glue/webview_delegate.h
index eafd383..1ccc761 100644
--- a/webkit/glue/webview_delegate.h
+++ b/webkit/glue/webview_delegate.h
@@ -231,11 +231,15 @@ class WebViewDelegate : virtual public WebWidgetDelegate {
   // Notifies that a new script context has been created for this frame.
   // This is similar to WindowObjectCleared but only called once per frame
   // context.
-  virtual void DidCreateScriptContext(WebFrame* webframe) {
+  virtual void DidCreateScriptContextForFrame(WebFrame* webframe) {
   }
 
   // Notifies that this frame's script context has been destroyed.
-  virtual void DidDestroyScriptContext(WebFrame* webframe) {
+  virtual void DidDestroyScriptContextForFrame(WebFrame* webframe) {
+  }
+
+  // Notifies that a garbage-collected context was created - content scripts.
+  virtual void DidCreateIsolatedScriptContext(WebFrame* webframe) {
   }
 
   // PolicyDelegate ----------------------------------------------------------