No longer relaunch into metro mode by default on touch devices.

chrome/common/pref_names.cc

Index: chrome/common/pref_names.cc
diff --git a/chrome/common/pref_names.cc b/chrome/common/pref_names.cc
index edf2729a9dad6c6042cf9471e93b82b74707551b..249028d845c1511d4e50f65d9991a41bf9e1ac58 100644
--- a/chrome/common/pref_names.cc
+++ b/chrome/common/pref_names.cc
@@ -1005,14 +1005,6 @@ const char kPluginsResourceCacheUpdate[] = "plugins.resource_cache_update";
 // on start-up.
 const char kCheckDefaultBrowser[] = "browser.check_default_browser";
 
-#if defined(OS_WIN)
-// By default, setting Chrome as default during first run on Windows 8 will
-// trigger shutting down the current instance and spawning a new (Metro)
-// Chrome. This boolean preference suppresses this behaviour.
-const char kSuppressSwitchToMetroModeOnSetDefault[] =
-    "browser.suppress_switch_to_metro_mode_on_set_default";

[gab, 2014/06/12 18:00:24]

Typically when phasing out prefs we still register them for some time followed
by a single ClearPref call to be removed after some time, e.g.
https://code.google.com/p/chromium/codesearch#chromium/src/chrome/browser/pre...

In this case it's probably not even relevant to cleanup this pref for a
milestone or two as it was probably only used as a master pref and it's not like
cleaning it will drastically reduce the bloat in the pref file, WDYT?

[grt (UTC plus 2), 2014/06/12 18:29:15]

Thanks for bringing this up. As we discussed, we'll forget about it. The number
of installs with this setting is likely to be spectacularly small.

-#endif
-
 // Policy setting whether default browser check should be disabled and default
 // browser registration should take place.
 const char kDefaultBrowserSettingEnabled[] =