Resize only the virtual viewport when the OSK triggers a resize.

chrome/android/java/src/org/chromium/chrome/browser/InsetConsumerView.java

+// Copyright 2016 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.
+
+package org.chromium.chrome.browser;
+
+import android.annotation.SuppressLint;
+import android.content.Context;
+import android.graphics.Rect;
+import android.os.Build;
+import android.util.AttributeSet;
+import android.view.WindowInsets;
+import android.widget.FrameLayout;
+
+import org.chromium.chrome.browser.tabmodel.TabModelSelector;
+import org.chromium.content.browser.ContentViewCore;
+
+/**
+ * The purpose of this view is to consume the insets (OSK resizes, status bar).
+ * It stores the value of the insets in ContentViewCore so that size of things
+ * like the OSK can be known.
+ */
+public class InsetConsumerView extends FrameLayout {
+
+    private TabModelSelector mTabModelSelector;
+
+    /**
+     * Creates an {@link InsetConsumerView}.
+     *
+     * @param context The Context to create this {@link InsetConsumerView} in.
+     */
+    public InsetConsumerView(Context context) {
+        super(context);
+    }
+
+    /**
+     * Creates an {@link InsetConsumerView}.
+     *
+     * @param context The Context to create this {@link InsetConsumerView} in.
+     * @param attrs The AttributeSet used to create this
+     *            {@link InsetConsumerView}.
+     */
+    public InsetConsumerView(Context context, AttributeSet attrs) {
+        super(context, attrs);
+    }
+
+    /**
+     * Sets the {@link TabModelSelector} that will be queried for information
+     * about the state of the system.
+     *
+     * @param tabModelSelector A {@link TabModelSelector} that represents the
+     *            state of the system.
+     */
+    public void setTabModelSelector(TabModelSelector tabModelSelector) {
+        mTabModelSelector = tabModelSelector;
+    }
+
+    @Deprecated

[aelias_OOO_until_Jul13, 2016/01/28 05:04:55]

It's not conventional to mark something like this deprecated, that's for API
surfaces, whereas this is an implementation detail.

Other code that makes use of deprecated APIs does
@SuppressWarnings("deprecation")

[ymalik, 2016/02/11 01:06:22]

Makes sense. Thanks!

+    @Override
+    protected boolean fitSystemWindows(Rect insets) {
+        // For Lollipop and above, onApplyWindowInsets will set the insets on
+        // ContentViewCore.
+        if (Build.VERSION.SDK_INT < Build.VERSION_CODES.LOLLIPOP
+                && mTabModelSelector != null && mTabModelSelector.getCurrentTab() != null) {
+            ContentViewCore cvc = mTabModelSelector.getCurrentTab().getContentViewCore();
+            if (cvc != null) {
+                cvc.setWindowInsets(new Rect(insets));

[aelias_OOO_until_Jul13, 2016/01/28 05:04:55]

I don't see any reason to use 'new' here instead of just passing the original
object.

[ymalik, 2016/02/11 01:06:22]

See comment below.

+            }
+        }
+        return super.fitSystemWindows(insets);
+    }
+
+    @SuppressLint("NewApi")

[aelias_OOO_until_Jul13, 2016/01/28 05:04:55]

I think the correct annotation is @TargetApi(Build.VERSION_CODES.LOLLIPOP)

[ymalik, 2016/02/11 01:06:22]

Done. Thanks!

+    @Override
+    public WindowInsets onApplyWindowInsets(WindowInsets insets) {
+        if (mTabModelSelector != null && mTabModelSelector.getCurrentTab() != null) {
+            ContentViewCore cvc = mTabModelSelector.getCurrentTab().getContentViewCore();
+            if (cvc != null) {
+                cvc.setWindowInsets(new WindowInsets(insets));

[aelias_OOO_until_Jul13, 2016/01/28 05:04:55]

Likewise, I don't see any reason to use 'new' here instead of just passing the
original object.

[ymalik, 2016/02/11 01:06:22]

You're right, there is no need for new in this case because we were just setting
the rect in CVC.

The reason I had 'new' here is because the actual insets eventually become 0
when they're fully consumed. In this particular case, we are only setting the
insets in cvc so we can read it later and not to actually apply any inset
setting logic. Thus, 'new' ensures that the function you're calling doesn't
actually mess with the inset setting logic in an instance where it modifies the
actual inset object.

In any case, I changed the function in CVC to take the four insets as params
which makes this a little clearer.  

+            }
+        }
+        return super.onApplyWindowInsets(insets);
+    }
+}