Do not display lock for hosted domains

chrome/browser/ui/cocoa/profiles/profile_chooser_controller.mm

Index: chrome/browser/ui/cocoa/profiles/profile_chooser_controller.mm
diff --git a/chrome/browser/ui/cocoa/profiles/profile_chooser_controller.mm b/chrome/browser/ui/cocoa/profiles/profile_chooser_controller.mm
index b90c224829c609200234f69ba377c858882eb9f7..75f92689bfd7db92941054224768984bff9916be 100644
--- a/chrome/browser/ui/cocoa/profiles/profile_chooser_controller.mm
+++ b/chrome/browser/ui/cocoa/profiles/profile_chooser_controller.mm
@@ -1722,6 +1722,11 @@ class ActiveProfileObserverBridge : public AvatarMenuObserver,
                                   IDS_PROFILES_PROFILE_SIGNOUT_BUTTON)
                   imageResourceId:IDR_ICON_PROFILES_MENU_LOCK
                            action:@selector(lockProfile:)];
+
+    if (!browser_->profile()->GetPrefs()->GetBoolean(
+        prefs::kProfileIsLockable)) {

[noms (inactive), 2014/09/12 19:33:26]

I don't think we should display the button at all if it's unusable (we don't for
local profiles). Maybe the caller of createOptionsViewWithRect should just pass
displayLock:NO

[Mike Lerman, 2014/09/15 14:08:56]

Chatted on one bug or another (I can find it if you like) about this with Alan
and Travis - we opted for showing it disabled. If something is disabled by
policy the standard is to show it disabled.

+      [lockButton setEnabled:NO];
+    }
     [container addSubview:lockButton];
     viewRect.origin.y = NSMaxY([lockButton frame]);