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

content/browser/web_contents/navigation_entry_impl.h

Index: content/browser/web_contents/navigation_entry_impl.h
diff --git a/content/browser/web_contents/navigation_entry_impl.h b/content/browser/web_contents/navigation_entry_impl.h
index f69cec9a2a879f6ec1c79fb84e314ca62369776e..4ca5aacabd80dd66403543b1e8392caed93a148f 100644
--- a/content/browser/web_contents/navigation_entry_impl.h
+++ b/content/browser/web_contents/navigation_entry_impl.h
@@ -73,6 +73,8 @@ class CONTENT_EXPORT NavigationEntryImpl
   virtual base::Time GetTimestamp() const OVERRIDE;
   virtual void SetCanLoadLocalResources(bool allow) OVERRIDE;
   virtual bool GetCanLoadLocalResources() const OVERRIDE;
+  virtual void SetFrameToNavigate(const std::string& frame_name) OVERRIDE;
+  virtual const std::string& GetFrameToNavigate() const OVERRIDE;
 
   void set_unique_id(int unique_id) {
     unique_id_ = unique_id;
@@ -259,6 +261,9 @@ class CONTENT_EXPORT NavigationEntryImpl
   // value is not needed after the entry commits and is not persisted.
   bool can_load_local_resources_;
 
+  // If not empty, the name of the frame to navigate.

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

Should this be persisted?  (See the warning above.)

I would worry about a restored tab sending the navigation to the main frame
instead of the intended subframe, even if this is only used in tests.

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

I'd rather not persist test-only data. I added a DCHECK to the session restore
system to make sure this doesn't happen accidentally.

+  std::string frame_to_navigate_;
+
   // Copy and assignment is explicitly allowed for this class.
 };