Plumbing toward transitioning remote frame back to a local frame.

Source/core/frame/FrameClient.h

 // Copyright 2014 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 FrameClient_h
 #define FrameClient_h
 
 namespace blink {
 
 class Frame;
 class LocalFrame;
 class MessageEvent;
+class ResourceRequest;
 class SecurityOrigin;
 
 class FrameClient {
 public:
     virtual Frame* opener() const = 0;
     virtual void setOpener(Frame*) = 0;
 
     virtual Frame* parent() const = 0;
     virtual Frame* top() const = 0;
     virtual Frame* previousSibling() const = 0;
     virtual Frame* nextSibling() const = 0;
     virtual Frame* firstChild() const = 0;
     virtual Frame* lastChild() const = 0;
 
     // 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() { }
 };
 
 } // namespace blink
 
 #endif // FrameClient_h