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

content/public/browser/navigation_entry.h

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef CONTENT_PUBLIC_BROWSER_NAVIGATION_ENTRY_H_
 #define CONTENT_PUBLIC_BROWSER_NAVIGATION_ENTRY_H_
 
 #include <string>
 
 #include "base/memory/ref_counted_memory.h"
@@ skipping 164 matching lines @@
   //   - this navigation was restored and for some reason the
   //     timestamp wasn't available;
   //   - or this navigation was copied from a foreign session.
   virtual void SetTimestamp(base::Time timestamp) = 0;
   virtual base::Time GetTimestamp() const = 0;
 
   // Used to specify if this entry should be able to access local file://
   // 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
 
 #endif  // CONTENT_PUBLIC_BROWSER_NAVIGATION_ENTRY_H_