Experiment with emulating mouse hover with touch hover capable devices

chrome/browser/about_flags.cc

Index: chrome/browser/about_flags.cc
diff --git a/chrome/browser/about_flags.cc b/chrome/browser/about_flags.cc
index 5aff454e3998d22adc9da31788f3d1660554f4d6..b1a75d7de634e01aaf640cc6b8987d3331ea8efb 100644
--- a/chrome/browser/about_flags.cc
+++ b/chrome/browser/about_flags.cc
@@ -1999,6 +1999,14 @@ const Experiment kExperiments[] = {
     SINGLE_VALUE_TYPE(extensions::switches::kEnableRemoteAssistance)
   },
 #endif  // defined(OS_CHROMEOS)
+  {
+    "enable-support-for-hover-capable-touchscreens",

[tdresser, 2014/10/30 13:00:05]

This is more verbose than necessary.

What about --enable-touch-hover?

+    IDS_FLAGS_ENABLE_SUPPORT_HOVER_CAPABLE_TOUCHSCREENS_NAME,

[tdresser, 2014/10/30 13:00:05]

This could probably also be made more concise.

ENABLE_TOUCH_HOVER or
ENABLE_TOUCHSCREEN_HOVER

+    IDS_FLAGS_ENABLE_SUPPORT_HOVER_CAPABLE_TOUCHSCREENS_DESCRIPTION,
+    kOsAndroid,
+    SINGLE_VALUE_TYPE("enable-support-for-hover-capable-touchscreens")
+  },
+
   // NOTE: Adding new command-line switches requires adding corresponding
   // entries to enum "LoginCustomFlags" in histograms.xml. See note in
   // histograms.xml and don't forget to run AboutFlagsHistogramTest unit test.