Switch the inheritance of WebView from WebWidget to protected.

content/shell/renderer/layout_test/layout_test_content_renderer_client.cc

Index: content/shell/renderer/layout_test/layout_test_content_renderer_client.cc
diff --git a/content/shell/renderer/layout_test/layout_test_content_renderer_client.cc b/content/shell/renderer/layout_test/layout_test_content_renderer_client.cc
index 317fe7815c4699c60a4d843c9504dd0132a39052..f1084629abda557837cf5a43e8e37d72f4204ae0 100644
--- a/content/shell/renderer/layout_test/layout_test_content_renderer_client.cc
+++ b/content/shell/renderer/layout_test/layout_test_content_renderer_client.cc
@@ -36,6 +36,7 @@
 
 using blink::WebAudioDevice;
 using blink::WebClipboard;
+using blink::WebFrame;
 using blink::WebLocalFrame;
 using blink::WebMIDIAccessor;
 using blink::WebMIDIAccessorClient;
@@ -101,6 +102,12 @@ void LayoutTestContentRendererClient::RenderThreadStarted() {
 void LayoutTestContentRendererClient::RenderFrameCreated(
     RenderFrame* render_frame) {
   new LayoutTestRenderFrameObserver(render_frame);
+
+  test_runner::WebTestProxyBase* proxy =

[dcheng, 2016/05/03 09:27:13]

The ultimate goal here is to associate the widget with the test proxy for the
RenderFrame, right? Do you have a sense of how involved that would be? Would it
make sense to group that into this CL?

[Łukasz Anforowicz, 2016/05/03 16:09:55]

Would it make sense to pass web_local_frame->frameWidget() to
WebFrameTestProxyBase and store it there?  (because WebFrameTestProxyBase is for
frame-level things, and WebTestProxyBase is for view-level things [I need to
rename it to WebViewTestProxyBase one day]).

[lfg, 2016/05/03 21:19:43]

I think that does make sense, but there's also a lot more involved in fixing
this. All over the test runner there are assumptions of a single widget (and
that being the WebView).

I think we need to fix the test runner to make it aware of local roots and
WebFrameWidgets, similarly to what we have with the WebFrameTestClient and
WebViewTestClient, we should look into adding a WebWidgetTestClient that
forwards things to RenderWidget when a local root is not the WebView.

Overall, I think this should be done separately.

[dcheng, 2016/05/04 04:55:29]

OK. Might be worth adding a TODO, but I leave that to you.

[dcheng, 2016/05/04 04:55:29]

OK. Might be worth adding a TODO, but I leave that to you.

+      GetWebTestProxyBase(render_frame->GetRenderView());
+  WebLocalFrame* frame = render_frame->GetWebFrame();
+  if (!frame->parent())
+    proxy->set_web_widget(frame->frameWidget());
 }
 
 void LayoutTestContentRendererClient::RenderViewCreated(
@@ -108,7 +115,6 @@ void LayoutTestContentRendererClient::RenderViewCreated(
   new ShellRenderViewObserver(render_view);
 
   test_runner::WebTestProxyBase* proxy = GetWebTestProxyBase(render_view);
-  proxy->set_web_widget(render_view->GetWebView());
   proxy->set_web_view(render_view->GetWebView());
   proxy->Reset();
   proxy->SetSendWheelGestures(UseGestureBasedWheelScrolling());