Allow Chrome OS login profile to have different default pref values

components/browser_context_keyed_service/browser_context_keyed_base_factory.cc

Index: components/browser_context_keyed_service/browser_context_keyed_base_factory.cc
diff --git a/components/browser_context_keyed_service/browser_context_keyed_base_factory.cc b/components/browser_context_keyed_service/browser_context_keyed_base_factory.cc
index 8d134f8164e089c3a438ee3e702e6f6cbee2275a..e6caa69d63c9792a3ec7ccf74b0975ab24c1d6c1 100644
--- a/components/browser_context_keyed_service/browser_context_keyed_base_factory.cc
+++ b/components/browser_context_keyed_service/browser_context_keyed_base_factory.cc
@@ -58,7 +58,7 @@ void BrowserContextKeyedBaseFactory::RegisterUserPrefsOnBrowserContext(
   // TestingBrowserContexts throw a wrench into the mix, in that some tests will
   // swap out the PrefService after we've registered user prefs on the original
   // PrefService. Test code that does this is responsible for either manually
-  // invoking RegisterUserPrefs() on the appropriate
+  // invoking RegisterProfilePrefs() on the appropriate
   // BrowserContextKeyedServiceFactory associated with the prefs they need,
   // or they can use SetTestingFactory() and create a service (since service
   // creation with a factory method causes registration to happen at service
@@ -77,7 +77,7 @@ void BrowserContextKeyedBaseFactory::RegisterUserPrefsOnBrowserContext(
     user_prefs::PrefRegistrySyncable* registry =
         static_cast<user_prefs::PrefRegistrySyncable*>(
             prefs->DeprecatedGetPrefRegistry());
-    RegisterUserPrefs(registry);
+    RegisterProfilePrefs(registry);
     registered_preferences_.insert(context);
   }
 }