Add loadCommit and loadStop Event

content/renderer/browser_plugin/browser_plugin.h

Index: content/renderer/browser_plugin/browser_plugin.h
diff --git a/content/renderer/browser_plugin/browser_plugin.h b/content/renderer/browser_plugin/browser_plugin.h
index 45ae96d09a691c0183cc628fcfa455306bd19031..d10447f1a5b83d321eee3500a55b533f5dd9348c 100644
--- a/content/renderer/browser_plugin/browser_plugin.h
+++ b/content/renderer/browser_plugin/browser_plugin.h
@@ -52,8 +52,11 @@ class CONTENT_EXPORT BrowserPlugin :
                   const BrowserPluginMsg_UpdateRect_Params& params);
   // Inform the BrowserPlugin that its guest has crashed.
   void GuestCrashed();
-  // Informs the BrowserPlugin that the guest has navigated to a new URL.
-  void DidNavigate(const GURL& url, int process_id);
+
+  // Inform the BrowserPlugin that the guest has finished loading a new page.
+  void LoadStop();
+  // Inform the BrowserPlugin that the guest has navigated to a new URL.
+  void LoadCommit(const GURL& url, int process_id, bool is_top_level);

[Fady Samuel, 2012/10/11 15:25:36]

FYI, this conflicts with my patch http://codereview.chromium.org/11092023/.
Depending on which one of us lands first, one of us will have to do a little bit
of rebasing. :-)

[irobert, 2012/10/11 16:50:44]

Sure. Since we are planning to remove this DidNavigate API, and I have already
replace the code which call this API with the LoadCommit API. I think you can
land first and I can rebase based on your commit. 

I don't know whether it is ok or not. 

On 2012/10/11 15:25:36, Fady Samuel wrote:

   // Inform the BrowserPlugin that the guest has started loading a new page.
   void LoadStart(const GURL& url, bool is_top_level);
   // Inform the BrowserPlugin that the guest has aborted loading a new page.