Plumbing toward transitioning remote frame back to a local frame.

Source/core/frame/FrameClient.h

Index: Source/core/frame/FrameClient.h
diff --git a/Source/core/frame/FrameClient.h b/Source/core/frame/FrameClient.h
index 3d388af7e400acfa0dedc1363c59a1455bb4e504..c21928f75ebce4759e89767d6875b3283a8e3f58 100644
--- a/Source/core/frame/FrameClient.h
+++ b/Source/core/frame/FrameClient.h
@@ -10,6 +10,7 @@ namespace blink {
 class Frame;
 class LocalFrame;
 class MessageEvent;
+class ResourceRequest;
 class SecurityOrigin;
 
 class FrameClient {
@@ -27,6 +28,9 @@ public:
     // Returns true if the embedder intercepted the postMessage call
     virtual bool willCheckAndDispatchMessageEvent(SecurityOrigin* /*target*/, MessageEvent*, LocalFrame* /*sourceFrame*/) const { return false; }
 
+    // Remote frame only:
+    virtual void navigate(const ResourceRequest&, bool shouldReplaceCurrentEntry) { }

[Nate Chapin, 2014/09/17 19:42:54]

Should we create a RemoteFrameClient/RemoteFrameClientImpl abstraction?
RemoteFrameClient is currently defined entirely in Source/web/

[dcheng, 2014/09/17 21:38:25]

I think this makes sense. We didn't need it initially, which is the reason it
currently only lives in Source/web

+
     virtual ~FrameClient() { }
 };