Add "frame to navigate" to NavigationEntry and plumb it to the RenderViewImpl

content/public/browser/navigation_entry.h

Index: content/public/browser/navigation_entry.h
diff --git a/content/public/browser/navigation_entry.h b/content/public/browser/navigation_entry.h
index 63af6871b20e202b7d796960e9d298c9d86e2a35..bceb6da2f112cae53c665068cfac528795daccdd 100644
--- a/content/public/browser/navigation_entry.h
+++ b/content/public/browser/navigation_entry.h
@@ -182,6 +182,11 @@ class NavigationEntry {
   // resources.
   virtual void SetCanLoadLocalResources(bool allow) = 0;
   virtual bool GetCanLoadLocalResources() const = 0;
+
+  // Used to specify which frame to navigate. If empty, the main frame is
+  // navigated.
+  virtual void SetFrameToNavigate(const std::string& frame_name) = 0;

[Charlie Reis, 2013/01/23 01:38:45]

I suppose this is a name rather than a frame ID because of how the layout tests
work?  An ID could probably locate any frame rather than just the named ones,
but maybe that's not useful.

[jochen (gone - plz use gerrit), 2013/01/23 08:22:42]

Yes, it's the (unique) name. In a layout test, we can't hard code the frame id
since they're generated on the fly.

+  virtual const std::string& GetFrameToNavigate() const = 0;
 };
 
 }  // namespace content