Remove pref store initialization check from

ForceKeyboardDrivenUINavigation in input device settings. This fixes a
focus issue when using keyboard navigation in CfM's.

Bug: b:148967469
Change-Id: I20567ce2a4616d80a966401c5b506c98372bca27
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2088012
Commit-Queue: Juan Pablo De Lima <jpdelima@chromium.org>
Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Cr-Commit-Position: refs/heads/master@{#752328}

chrome/browser/chromeos/preferences.cc

@@ -374,7 +374,12 @@ void Preferences::RegisterProfilePrefs(
   bool allow_time_zone_resolve_by_default = true;
   // CfM devices default to static timezone unless time zone resolving is
   // explicitly enabled for the signin screen (usually by policy).
-  if (system::InputDeviceSettings::Get()->ForceKeyboardDrivenUINavigation() &&
+  // We need local_state fully initialized, which does not happen in tests.
+  if (!g_browser_process->local_state() ||
+      g_browser_process->local_state()
+              ->GetAllPrefStoresInitializationStatus() ==
+          PrefService::INITIALIZATION_STATUS_WAITING ||
+      system::InputDeviceSettings::Get()->ForceKeyboardDrivenUINavigation() ||
       !system::TimeZoneResolverManager::
           IfServiceShouldBeRunningForSigninScreen()) {
     allow_time_zone_resolve_by_default = false;

chrome/browser/chromeos/system/input_device_settings.cc

@@ -353,10 +353,7 @@ bool InputDeviceSettings::ForceKeyboardDrivenUINavigation() {
   // tests do not have InstallAttributes or LocalState initialized, so getting
   // browser_policy_connector crashes.
   if (!InstallAttributes::IsInitialized() ||
-      !g_browser_process->local_state() ||
-      g_browser_process->local_state()
-              ->GetAllPrefStoresInitializationStatus() ==
-          PrefService::INITIALIZATION_STATUS_WAITING) {
+      !g_browser_process->local_state()) {
     return false;
   }