Tapping handle shouldn't select misspelled word

content/browser/renderer_host/render_widget_host_view_android.cc

Index: content/browser/renderer_host/render_widget_host_view_android.cc
diff --git a/content/browser/renderer_host/render_widget_host_view_android.cc b/content/browser/renderer_host/render_widget_host_view_android.cc
index 3d5e597188c7408a5d07df7f34927b96ab9a78e0..8f1d5eef391d4765f65e76439eee2da68908b0e7 100644
--- a/content/browser/renderer_host/render_widget_host_view_android.cc
+++ b/content/browser/renderer_host/render_widget_host_view_android.cc
@@ -1823,7 +1823,7 @@ void RenderWidgetHostViewAndroid::MoveCaret(const gfx::Point& point) {
 void RenderWidgetHostViewAndroid::ShowContextMenuAtPoint(
     const gfx::Point& point) {
   if (host_)
-    host_->ShowContextMenuAtPoint(point);
+    host_->ShowContextMenuAtPoint(point, true);

[bokan, 2017/05/09 23:21:36]

I'm not sure I understand, why are all context menus on Android always from a
touch handle?

[yosin_UTC9, 2017/05/10 04:39:49]

Agree with bokan@. We want to know how context menu invoked, e.g. long tap,
selection handle tap, etc.
It seems pass around a reason of context menu invocation is better than |bool|.

 }
 
 void RenderWidgetHostViewAndroid::DismissTextHandles() {