Android - Introduce "keyboard accessory" for Autofill suggestions.

ui/android/java/src/org/chromium/ui/base/WindowAndroid.java

Index: ui/android/java/src/org/chromium/ui/base/WindowAndroid.java
diff --git a/ui/android/java/src/org/chromium/ui/base/WindowAndroid.java b/ui/android/java/src/org/chromium/ui/base/WindowAndroid.java
index 0bf7bd1ade48d9faf55f2c80dffaa5e696475318..7d991268a6b02ffb97d752daf778104c85e971db 100644
--- a/ui/android/java/src/org/chromium/ui/base/WindowAndroid.java
+++ b/ui/android/java/src/org/chromium/ui/base/WindowAndroid.java
@@ -16,6 +16,7 @@ import android.os.Bundle;
 import android.util.Log;
 import android.util.SparseArray;
 import android.view.View;
+import android.view.ViewGroup;
 import android.widget.Toast;
 
 import org.chromium.base.CalledByNative;
@@ -55,6 +56,8 @@ public class WindowAndroid {
     private HashSet<Animator> mAnimationsOverContent = new HashSet<Animator>();
     private View mAnimationPlaceholderView;
 
+    private ViewGroup mKeyboardAccessoryView;
+
     private final VSyncMonitor.Listener mVSyncListener = new VSyncMonitor.Listener() {
         @Override
         public void onVSync(VSyncMonitor monitor, long vsyncTimeMicros) {
@@ -326,6 +329,19 @@ public class WindowAndroid {
     }
 
     /**
+     * Sets the keyboard accessory view.
+     * This view sits at the bottom of the content area and pushes the content up rather than
+     * overlaying it. Currently used as a container for Autofill suggestions.

[David Trainor- moved to gerrit, 2015/04/20 23:29:44]

add @param view and describe the viewgroup there imo.  We probably should have
done it for the placeholder view above earlier.  I missed that one!

[Evan Stade, 2015/04/21 00:48:52]

Done.

+     */
+    public void setKeyboardAccessoryView(ViewGroup view) {
+        mKeyboardAccessoryView = view;
+    }
+
+    public ViewGroup getKeyboardAccessoryView() {

[David Trainor- moved to gerrit, 2015/04/20 23:29:43]

Javadoc

[Evan Stade, 2015/04/21 00:48:52]

I can't think of a doc that makes this any easier to understand than it is
already. That is, most things I could write would be redundant with the docs for
setKeyboardAccessoryView. Do you have a suggestion for what you'd like to see
here?

[David Trainor- moved to gerrit, 2015/04/21 06:55:47]

I'd be fine with an {@see #setKeyboardAccessoryView(ViewGroup)}, but yeah I see
your point. :)

[Evan Stade, 2015/04/21 18:10:30]

Done.

+        return mKeyboardAccessoryView;
+    }
+
+    /**
      * Start a post-layout animation on top of web content.
      *
      * By default, Android optimizes what it shows on top of SurfaceViews (saves power).