Make content_browsertests for Chrome on Android running with valid Views

content/public/android/java/src/org/chromium/content/browser/ContentViewRenderView.java

Index: content/public/android/java/src/org/chromium/content/browser/ContentViewRenderView.java
diff --git a/content/public/android/java/src/org/chromium/content/browser/ContentViewRenderView.java b/content/public/android/java/src/org/chromium/content/browser/ContentViewRenderView.java
index 950ea3bb211e9737ad1c3ba9ffe95b321919c65b..4d3f5711c72b15a5455dd538d036336d8a9f7f47 100644
--- a/content/public/android/java/src/org/chromium/content/browser/ContentViewRenderView.java
+++ b/content/public/android/java/src/org/chromium/content/browser/ContentViewRenderView.java
@@ -103,6 +103,17 @@ public class ContentViewRenderView extends FrameLayout {
         mContentReadbackHandler.initNativeContentReadbackHandler();
     }
 
+    @Override
+    protected void onSizeChanged(int wPix, int hPix, int owPix, int ohPix) {
+        // If mContentViewCore was initialized too early, physical backing size is empty.
+        // In this case, we should resize it before viewport size is set.

[Jaekyun Seok (inactive), 2015/02/12 08:33:54]

I'm not sure whether this could be a solution for the problem that
RenderWidgetHostImpl::OnUpdateRect() isn't called.

But I confirmed that it wasn't called when viewport size was set before valid
physical backing size was set.

Such thing is happening only on ContentShell and ContentBrowserTests, not on
ChromeShell and Chrome.

[Jaekyun Seok (inactive), 2015/02/13 10:15:22]

I found that resizing ack is ignored in
https://cs.corp.google.com/#clankium/src/content/renderer/render_widget.cc&l=822
when only physical backing size is changed.

So RenderWidgetHostImpl::OnUpdateRect() can be called only if viewport size is
changed.

That is why RenderWidgetHostImpl::OnUpdateRect() isn't called when viewport size
is set before valid physical backing size is set.

I tried to modify RenderWidget::Resize(), but I failed to make a proper change.

Daniel, are you OK with this workaround? Or do you have any better idea to fix
the resizing ack?

[no sievers, 2015/02/21 00:45:54]

These changes in here shouldn't be needed. I think
https://codereview.chromium.org/948603002/ takes care of the problem, and I
described it over there.

[Jaekyun Seok (inactive), 2015/02/23 10:41:34]

I confirmed that your CL resolved the resizing problem. I will remove these
changes after your CL is landed.

+        if (mContentViewCore != null && mContentViewCore.getPhysicalBackingWidthPix() == 0
+                && mContentViewCore.getPhysicalBackingHeightPix() == 0) {
+            mContentViewCore.onPhysicalBackingSizeChanged(wPix, hPix);
+        }
+        super.onSizeChanged(wPix, hPix, owPix, ohPix);
+    }
+
     /**
      * @return The content readback handler.
      */