Tapping handle shouldn't select misspelled word

ui/base/ui_base_types.h

Index: ui/base/ui_base_types.h
diff --git a/ui/base/ui_base_types.h b/ui/base/ui_base_types.h
index b07dca26392f981faa4f69dfb406a7a5b34a8f61..7eaf0e0b1693ab60acbea7e13219dce1ccb9fcc4 100644
--- a/ui/base/ui_base_types.h
+++ b/ui/base/ui_base_types.h
@@ -48,7 +48,8 @@ enum MenuSourceType {
   MENU_SOURCE_TOUCH_EDIT_MENU = 4,
   MENU_SOURCE_LONG_PRESS      = 5,
   MENU_SOURCE_LONG_TAP        = 6,
-  MENU_SOURCE_TYPE_LAST = MENU_SOURCE_LONG_TAP
+  MENU_SOURCE_TOUCH_HANDLE    = 7,

[sadrul, 2017/05/25 04:13:50]

Can you just use MENU_SOURCE_TOUCH_EDIT_MENU? Because that's what aura uses for
this.

[amaralp1, 2017/05/25 04:39:53]

Isn't MENU_SOURCE_TOUCH_EDIT_MENU used when you tap the ellipses option in the
floating menu? This would be used for when you tap the insertion handle and have
the floating paste menu show up. Android now sends a context menu event in this
scenario and I think Aura doesn't. I think it would be better to keep these two
scenarios separate since eventually Aura may want to trigger the floating menus
with context menu events.

[sadrul, 2017/05/25 21:24:15]

Thanks for the explanation. Makes sense to me.

+  MENU_SOURCE_TYPE_LAST = MENU_SOURCE_TOUCH_HANDLE
 };
 
 UI_BASE_EXPORT MenuSourceType GetMenuSourceTypeForEvent(const ui::Event& event);