To fix the cross-site post submission bug.

chrome/browser/ui/browser_navigator.h

Index: chrome/browser/ui/browser_navigator.h
diff --git a/chrome/browser/ui/browser_navigator.h b/chrome/browser/ui/browser_navigator.h
index 5df4136a0243f80a988448795cd27905cee9b319..f2ac443c92a3ff1cbd78568acd5536c5c1da8449 100644
--- a/chrome/browser/ui/browser_navigator.h
+++ b/chrome/browser/ui/browser_navigator.h
@@ -10,6 +10,7 @@
 #include "chrome/browser/ui/host_desktop.h"
 #include "content/public/browser/browser_context.h"
 #include "content/public/browser/global_request_id.h"
+#include "content/public/common/frame_navigate_params.h"
 #include "content/public/common/page_transition_types.h"
 #include "content/public/common/referrer.h"
 #include "googleurl/src/gurl.h"
@@ -19,6 +20,7 @@
 class Browser;
 class Profile;
 class TabContents;
+using content::ViewMsg_Request;

[michaeln, 2012/11/02 00:08:23]

please avoid the use of using declarations in .h files to avoid potential
namespace collisions

[irobert, 2012/11/02 17:22:55]

Done.

 
 namespace chrome {
 
@@ -203,6 +205,9 @@ struct NavigateParams {
   // explicitly or inferred from an existing Browser instance.
   chrome::HostDesktopType host_desktop_type;
 
+  // request
+  ViewMsg_Request request;

[michaeln, 2012/11/02 00:08:23]

There's some overlap between member of tha NavigateParams struct and members of
the new 'request' struct, in particular the 'url' members. The new info that's
missing from this struct seems to be the post data and the content type. I
wonder if the content type can go in the extra_headers field? The new transition
type implies 'POST' so not really sure we need the method string?

[irobert, 2012/11/02 17:22:55]

Yes. You are right. Since all the param structs in this path contain 'url' and
'extra header' field. I believe we can reuse them.

On 2012/11/02 00:08:23, michaeln wrote:

+
  private:
   NavigateParams();
 };