Experiment with emulating mouse hover with touch hover capable devices

chrome/app/generated_resources.grd

Index: chrome/app/generated_resources.grd
diff --git a/chrome/app/generated_resources.grd b/chrome/app/generated_resources.grd
index 2be1cb77c460f9bcf289d7f62dde633fb848c8d6..955f5793e389d4ab944bb8a7a104f7c9274d72da 100644
--- a/chrome/app/generated_resources.grd
+++ b/chrome/app/generated_resources.grd
@@ -14912,6 +14912,12 @@ Do you accept?
     <message name="IDS_DEVICE_PERMISSIONS_DIALOG_SELECT" desc="Button confirming the devices selected for access by the app.">
       Select
     </message>
+    <message name="IDS_FLAGS_ENABLE_TOUCH_HOVER_NAME" desc="Name of the 'Enable support for hover capable touchscreens' flag.">
+      Enable support for hover capable touchscreens
+    </message>
+    <message name="IDS_FLAGS_ENABLE_TOUCH_HOVER_DESCRIPTION" desc="Description of the 'Enable support for hover capable touchscreens' flag.">
+      Enables Finger Air View by holding your finger just over the screen to experience webpage magnifier or a mouseover event.

[Rick Byers, 2014/11/13 19:32:15]

nit: let's not use the Samsung specific feature term here - it's conceivable
that other Android devices could send touch hover events as well.  Also what's
the reference to 'webpage magnifier'?  I know that's what Samsung's chromium
fork does with the hover events, but we don't have any code for that upstream do
we? 

[lanwei, 2014/12/01 15:25:19]

Done.

+    </message>
   </messages>
   </release>
 </grit>