Fix some issues with extension messaging:

- Disconnect ports properly (javascript mistake).
- Use the right port ID when dispatching the disconnect event.
- Fix a bug with 2 extensions loaded in the same process.

BUG=12686
BUG=15798
TEST=Load an extension that uses messaging, and make sure it disconnects when you navigate or close the connecting.

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

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

1 files changed, 4 insertions, 1 deletions

diff --git a/chrome/renderer/extensions/event_bindings.cc b/chrome/renderer/extensions/event_bindings.cc
index 240c330..e9efbad 100644
--- a/chrome/renderer/extensions/event_bindings.cc
+++ b/chrome/renderer/extensions/event_bindings.cc
@@ -144,6 +144,10 @@ void EventBindings::HandleContextCreated(WebFrame* frame) {
       v8::Persistent<v8::Context>::New(context);
   GetContexts().push_back(linked_ptr<ContextInfo>(
       new ContextInfo(persistent_context, extension_id)));
+
+  v8::Handle<v8::Value> argv[1];
+  argv[0] = v8::String::New(extension_id.c_str());
+  CallFunctionInContext(context, "dispatchOnLoad", arraysize(argv), argv);
 }
 
 // static
@@ -182,7 +186,6 @@ void EventBindings::HandleContextDestroyed(WebFrame* frame) {
 // static
 void EventBindings::CallFunction(const std::string& function_name,
                                  int argc, v8::Handle<v8::Value>* argv) {
-  v8::HandleScope handle_scope;
   for (ContextList::iterator it = GetContexts().begin();
        it != GetContexts().end(); ++it) {
     CallFunctionInContext((*it)->context, function_name, argc, argv);