Handler shown in editable field should be removed on any key press on keypad.

content/public/android/java/src/org/chromium/content/browser/input/ImeAdapter.java

 // Copyright 2012 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.content.browser.input;
 
 import android.os.Handler;
 import android.os.ResultReceiver;
 import android.os.SystemClock;
 import android.text.Editable;
@@ skipping 343 matching lines @@
                 nativeSetComposingText(mNativeImeAdapterAndroid, text, textStr, newCursorPosition);
             }
             nativeSendSyntheticKeyEvent(mNativeImeAdapterAndroid, sEventTypeKeyUp,
                     timeStampMs, keyCode, 0);
         }
 
         return true;
     }
 
     void finishComposingText() {
         if (mNativeImeAdapterAndroid == 0) return;

[aurimas (slooooooooow), 2014/07/01 19:31:14]

Should we add a call to onImeEvent here as well?

[jdduke (slow), 2014/07/01 19:36:37]

I don't think so, and neither in the other functions you referenced.  Ideally
the |onImeEvent()| would correspond to synthetic/real key events being sent to
the renderer.  I think adding the call in |deleteSurroundingText()| should be
sufficient for now (the other cases are already handled by the response from the
renderer when the selection changes).

         nativeFinishComposingText(mNativeImeAdapterAndroid);
     }
 
     boolean translateAndSendNativeEvents(KeyEvent event) {
         if (mNativeImeAdapterAndroid == 0) return false;
 
         int action = event.getAction();
         if (action != KeyEvent.ACTION_DOWN &&
             action != KeyEvent.ACTION_UP) {
             // action == KeyEvent.ACTION_MULTIPLE
@@ skipping 24 matching lines @@
 
     /**
      * Send a request to the native counterpart to delete a given range of characters.
      * @param beforeLength Number of characters to extend the selection by before the existing
      *                     selection.
      * @param afterLength Number of characters to extend the selection by after the existing
      *                    selection.
      * @return Whether the native counterpart of ImeAdapter received the call.
      */
     boolean deleteSurroundingText(int beforeLength, int afterLength) {
+        mViewEmbedder.onImeEvent(false);
         if (mNativeImeAdapterAndroid == 0) return false;
         // Can't send the deletion key code yet because it will delete an extra char at the end.
         // Also the deleteSurroundingText message is not always ordered properly with key event
         // messages yet.
         // TODO(guohui): fix the ordering and send the deletion key code for single-char deletion.
         sendSyntheticKeyEvent(
                 sEventTypeRawKeyDown, SystemClock.uptimeMillis(), KeyEvent.KEYCODE_UNKNOWN, 0);
         nativeDeleteSurroundingText(mNativeImeAdapterAndroid, beforeLength, afterLength);
         sendSyntheticKeyEvent(
                 sEventTypeKeyUp, SystemClock.uptimeMillis(), KeyEvent.KEYCODE_UNKNOWN, 0);
         return true;
     }
 
     /**
      * Send a request to the native counterpart to set the selection to given range.
      * @param start Selection start index.
      * @param end Selection end index.
      * @return Whether the native counterpart of ImeAdapter received the call.
      */
     boolean setEditableSelectionOffsets(int start, int end) {
         if (mNativeImeAdapterAndroid == 0) return false;

[aurimas (slooooooooow), 2014/07/01 19:31:14]

Should we add a call to onImeEvent here as well?

         nativeSetEditableSelectionOffsets(mNativeImeAdapterAndroid, start, end);
         return true;
     }
 
     /**
      * Send a request to the native counterpart to set compositing region to given indices.
      * @param start The start of the composition.
      * @param end The end of the composition.
      * @return Whether the native counterpart of ImeAdapter received the call.
      */
     boolean setComposingRegion(int start, int end) {
         if (mNativeImeAdapterAndroid == 0) return false;

[aurimas (slooooooooow), 2014/07/01 19:31:14]

Should we add a call to onImeEvent here as well?

         nativeSetComposingRegion(mNativeImeAdapterAndroid, start, end);
         return true;
     }
 
     /**
      * Send a request to the native counterpart to unselect text.
      * @return Whether the native counterpart of ImeAdapter received the call.
      */
     public boolean unselect() {
         if (mNativeImeAdapterAndroid == 0) return false;
@@ skipping 139 matching lines @@
     private native void nativeDeleteSurroundingText(long nativeImeAdapterAndroid,
             int before, int after);
 
     private native void nativeUnselect(long nativeImeAdapterAndroid);
     private native void nativeSelectAll(long nativeImeAdapterAndroid);
     private native void nativeCut(long nativeImeAdapterAndroid);
     private native void nativeCopy(long nativeImeAdapterAndroid);
     private native void nativePaste(long nativeImeAdapterAndroid);
     private native void nativeResetImeAdapter(long nativeImeAdapterAndroid);
 }