Disable learning text suggestions if in incognito.

chrome/android/java/src/org/chromium/chrome/browser/omnibox/LocationBarLayout.java

Index: chrome/android/java/src/org/chromium/chrome/browser/omnibox/LocationBarLayout.java
diff --git a/chrome/android/java/src/org/chromium/chrome/browser/omnibox/LocationBarLayout.java b/chrome/android/java/src/org/chromium/chrome/browser/omnibox/LocationBarLayout.java
index 12c8848c7ca170597f804ab9d52277fc560f734d..d64daf274669521f97dda5d5154ba0a8e548d0b1 100644
--- a/chrome/android/java/src/org/chromium/chrome/browser/omnibox/LocationBarLayout.java
+++ b/chrome/android/java/src/org/chromium/chrome/browser/omnibox/LocationBarLayout.java
@@ -2249,15 +2249,18 @@ public class LocationBarLayout extends FrameLayout
         updateSecurityIcon(getSecurityLevel());
     }
 
-    /**
-     * @return The Tab currently showing.
-     */
     @Override
     public Tab getCurrentTab() {
         if (mToolbarDataProvider == null) return null;
         return mToolbarDataProvider.getTab();
     }
 
+    @Override
+    public boolean isIncognito() {
+        if (mToolbarDataProvider == null) return false;

[Changwan Ryu, 2017/05/23 19:47:47]

We actually set an empty version in ToolbarLayout#onFinishInflate(),
and set a real version after ToolbarLayout#initialize() which is part of post
inflation startup. If inputconnection is activated between the two calls, then
we may report the flag incorrectly, but likely not possible because
onFinishInflate() and initialize() will likely be called in one UI loop. Could
you confirm?

[Ted C, 2017/05/23 20:07:19]

The null check here is for consistency with above.  So this seems somewhat
orthogonal and whether we should investigate removing the null checks
entirely.

The reason I kept these here and I don't think it to be too terribly
unreasonable
is that these are called by Android methods on View/TextView.  I have no
control over whether the super constructor or onFinishInflate for TextView
will trigger an input connection create and thus call into this very early
in the construction flow before any of these calls you show are triggered.

So I guess I'm wondering what you want to be confirmed?

[Ted C, 2017/05/23 21:09:15]

Per the offline discussion, this was more around us opt-ing into keyboard
sharing when the state was unknown.  That is a great point and we shouldn't do
that.

Switched to default off until we can actually determine the incognito-ness.  All
the boolean logic should be inverted now.

+        return mToolbarDataProvider.isIncognito();
+    }
+
     private void initOmniboxResultsContainer() {
         if (mOmniboxResultsContainer != null) return;