Caret is showing after do a copy operation from editable field.

content/public/android/java/src/org/chromium/content/browser/ContentViewCore.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;
 
 import android.annotation.SuppressLint;
 import android.app.Activity;
 import android.app.SearchManager;
 import android.content.ContentResolver;
@@ skipping 2174 matching lines @@
                 return mFocusedNodeEditable;
             }
 
             @Override
             public void onDestroyActionMode() {
                 mActionMode = null;
                 if (mUnselectAllOnActionModeDismiss) {
                     if (isSelectionEditable()) {
                         int selectionEnd = Selection.getSelectionEnd(mEditable);
                         mInputConnection.setSelection(selectionEnd, selectionEnd);
+                        hideHandles();

[jdduke (slow), 2014/07/16 15:08:59]

Is there any downside to moving the |hideHandles()| call up so that it's called
for either case, i.e.,

if (mUnselectAllOnActionModeDismiss) {
    hideHandles();
    ...

The handles should naturally become hidden from |mImeAdapter.unselect()|, but an
explicit |hideHandles()| call would prevent the handles from automatically
appearing again if selection is activated outside a user gesture (could be
wrong).

[AKVT, 2014/07/16 16:39:09]

Thanks for reviewing.
mImeAdapter.unselect() takes care of hiding the handles by itself. For editable
case we are setting the selection to end, but not clearing(unselecting) the
selection. So caret stays. So hideHandles() is needed only for editable case
only. Also if user touches on the editable again later, handles started
appearing. Also if I trigger a selection after a copy using JS, that time also
selection handle appears.

[jdduke (slow), 2014/07/16 18:14:23]

I realize handles in a non-editable region are hidden via
|mImeAdapter.unselect()|, but I think we not only want to hide them but also
prevent them from automatically showing again, which is only accomplished via
|hideHandles()|.  I think we can accomplish both by moving the |hideHandles()|
call above the |isSelectionEditable()| if branch.

[AKVT, 2014/07/17 03:03:12]

Done.

                     } else {
                         mImeAdapter.unselect();
                     }
                 }
                 getContentViewClient().onContextualActionBarHidden();
             }
 
             @Override
             public boolean isShareAvailable() {
                 Intent intent = new Intent(Intent.ACTION_SEND);
@@ skipping 1187 matching lines @@
 
     private native void nativeExtractSmartClipData(long nativeContentViewCoreImpl,
             int x, int y, int w, int h);
     private native void nativeSetBackgroundOpaque(long nativeContentViewCoreImpl, boolean opaque);
 
     private native void nativeResumeResponseDeferredAtStart(
             long nativeContentViewCoreImpl);
     private native void nativeSetHasPendingNavigationTransitionForTesting(
             long nativeContentViewCoreImpl);
 }