Remove references to IsNewAvatarMenu since the flag was removed.

chrome/browser/ui/webui/options/manage_profile_handler.cc

Index: chrome/browser/ui/webui/options/manage_profile_handler.cc
diff --git a/chrome/browser/ui/webui/options/manage_profile_handler.cc b/chrome/browser/ui/webui/options/manage_profile_handler.cc
index 056c20c5bfd704e443821ca171cbe06bb766c4f4..04754bb452559bf7e73601686a5d2bb677b0b4ba 100644
--- a/chrome/browser/ui/webui/options/manage_profile_handler.cc
+++ b/chrome/browser/ui/webui/options/manage_profile_handler.cc
@@ -131,8 +131,6 @@ void ManageProfileHandler::GetLocalizedValues(
                                supervised_user_dashboard_url,
                                supervised_user_dashboard_display));
 
-  localized_strings->SetBoolean("newAvatarMenuEnabled",

[Mike Lerman, 2015/09/28 15:23:01]

What about ChromeOS?

[anthonyvd, 2015/09/29 20:23:16]

For context, you can take a look at the comments in the corresponding JS file
but basically the JS code that cares about this value is not accessible on
ChromeOS since they create users from the lock screen rather than the settings
page.

-                                switches::IsNewAvatarMenu());
   localized_strings->SetBoolean("profileShortcutsEnabled",
                                 ProfileShortcutManager::IsFeatureEnabled());