Implement WebFrameClient in RenderFrameImpl and proxy all calls to RenderView.

content/renderer/render_view_impl.cc

Index: content/renderer/render_view_impl.cc
diff --git a/content/renderer/render_view_impl.cc b/content/renderer/render_view_impl.cc
index 48314fd7820b21524aa9952b97d72d71f52640ca..ce4bfd474f9f389a1335c2f0899289c6f8f610fb 100644
--- a/content/renderer/render_view_impl.cc
+++ b/content/renderer/render_view_impl.cc
@@ -882,7 +882,7 @@ void RenderViewImpl::Initialize(RenderViewImplParams* params) {
       ShouldUseTransitionCompositing(device_scale_factor_));
 
   webkit_glue::ApplyWebPreferences(webkit_preferences_, webview());
-  webview()->initializeMainFrame(this);
+  webview()->initializeMainFrame(main_render_frame_.get());

[Charlie Reis, 2013/06/12 20:32:29]

Does RenderViewImpl still need to derive from WebFrameClient?  I know all its
WebFrameClient methods will stick around for a while, but that will let us start
removing them one-by-one.

[nasko, 2013/06/12 21:36:00]

I didn't want to touch the header file for RenderViewImpl for this change. If I
remove the derivation, I need to remove a bunch of OVERRIDE keywords. I agree it
shouldn't derive and if you feel the code churn is worth now, I'll do it.

[Charlie Reis, 2013/06/12 22:16:10]

I think we might as well.  It's conceptually tied to what you're doing here,
makes it so we keep only one WebFrameClient implementation, and sets you up to
start moving methods.

 
   if (switches::IsTouchDragDropEnabled())
     webview()->settings()->setTouchDragDropEnabled(true);