Honor owner tap-to-click and mouse buttons swap on login screen

chrome/browser/chrome_browser_main.cc

Index: chrome/browser/chrome_browser_main.cc
diff --git a/chrome/browser/chrome_browser_main.cc b/chrome/browser/chrome_browser_main.cc
index 6900a07bdf032eb18d5399f3da6e9664eab6929b..70a32c58e14e836d9d451542a1a5ccd0054256e1 100644
--- a/chrome/browser/chrome_browser_main.cc
+++ b/chrome/browser/chrome_browser_main.cc
@@ -273,9 +273,11 @@ PrefService* InitializeLocalState(const CommandLine& parsed_command_line,
   // are registered.
   local_state->RegisterStringPref(prefs::kApplicationLocale, std::string());
 #if defined(OS_CHROMEOS)
-  local_state->RegisterStringPref(prefs::kOwnerLocale, std::string());
   local_state->RegisterStringPref(prefs::kHardwareKeyboardLayout,

[sky, 2012/09/11 16:04:02]

It doesn't scale to add platform specific prefs to chrome_browser_main. Could we
move these to some where closer to chromeos and have chrome_browser_main call a
function to register all the chromeos specific prefs?

[achuithb, 2012/09/11 17:36:31]

Maybe here:
http://code.google.com/codesearch#OAMlx_jo-ck/src/chrome/browser/chromeos/chr...

[Dmitry Polukhin, 2012/09/12 11:32:12]

We don't have any prefs registration in chrome_browser_main_chromeos.cc. I moved
all chrome os specific prefs registration to WizardController where we register
several login/OOBE prefs already.

[Dmitry Polukhin, 2012/09/12 14:31:09]

Returned kOwnerLocale and kHardwareKeyboardLayout back because kOwnerLocale pref
is used later in this function. So I reverted all changes in
chrome_browser_main.cc.

                                   std::string());
+  local_state->RegisterStringPref(prefs::kOwnerLocale, std::string());
+  local_state->RegisterBooleanPref(prefs::kOwnerPrimaryMouseButtonRight, false);
+  local_state->RegisterBooleanPref(prefs::kOwnerTapToClickEnabled, true);
 #endif  // defined(OS_CHROMEOS)
 #if !defined(OS_CHROMEOS)
   local_state->RegisterBooleanPref(prefs::kMetricsReportingEnabled,