Add WebWidgetTestProxy.

components/test_runner/web_widget_test_client.h

Index: components/test_runner/web_widget_test_client.h
diff --git a/components/test_runner/web_widget_test_client.h b/components/test_runner/web_widget_test_client.h
index a5e9d5d1d1a87ccc23ba5a949fb7c8ce5bb93a5f..15113909abe7bb9a81386e56a1074380c695af83 100644
--- a/components/test_runner/web_widget_test_client.h
+++ b/components/test_runner/web_widget_test_client.h
@@ -18,6 +18,7 @@ namespace test_runner {
 class TestRunner;
 class WebTestDelegate;
 class WebViewTestProxyBase;
+class WebWidgetTestProxyBase;
 
 // WebWidgetTestClient implements WebWidgetClient interface, providing behavior
 // expected by tests.  WebWidgetTestClient ends up used by WebViewTestProxy
@@ -29,10 +30,15 @@ class WebWidgetTestClient : public blink::WebWidgetClient {
   // Caller has to ensure that all arguments (i.e. |test_runner| and |delegate|)
   // live longer than |this|.
   WebWidgetTestClient(TestRunner* test_runner,
-                      WebViewTestProxyBase* web_view_test_proxy_base);
+                      WebWidgetTestProxyBase* web_widget_test_proxy_base);
 
   virtual ~WebWidgetTestClient();
 
+  void set_web_view_test_proxy_base(
+      WebViewTestProxyBase* web_view_test_proxy_base) {
+    web_view_test_proxy_base_ = web_view_test_proxy_base;
+  }

[Łukasz Anforowicz, 2016/08/02 20:38:12]

This doesn't block this CL, but it's a pity that we still need the
web_view_test_proxy_base_ field (i.e. we need a sort of a widget -> view
dependency on the test side).  I think web_view_test_proxy_base_ field is only
used to 1) get TestRunner and TestInterfaces (which could be passed directly to
the WebWidgetTestClient's constructor and 2) to reach to view_test_runner to
interact with pointer lock API (which I have no idea what to do about - would
this belong on a widget in the long-term?).

[lfg, 2016/08/02 22:27:21]

Also related to 1, it's also being used to get the WebTestDelegate, which can
also be passed directly during/after construction.

However, for 2, unfortunately this does not belong to widget long-term. In
chrome the pointer lock API is handled by MouseLockController, which lives in
chrome/browser/. We could do some refactor to remove the pointer lock stuff from
TestRunnerForSpecificView, but the code needs to live in an object that's only
instantiated once, which is different from the lifetime of the widget. Since no
such place currently exists, I opted to leave the code in
TestRunnerForSpecifivView.

+
   // WebWidgetClient overrides needed by WebViewTestProxy.
   blink::WebScreenInfo screenInfo() override;
   void scheduleAnimation() override;
@@ -49,6 +55,7 @@ class WebWidgetTestClient : public blink::WebWidgetClient {
   // Borrowed pointers to other parts of Layout Tests state.
   TestRunner* test_runner_;
   WebViewTestProxyBase* web_view_test_proxy_base_;
+  WebWidgetTestProxyBase* web_widget_test_proxy_base_;
 
   bool animation_scheduled_;