When the new profile management flag is enabled, make sure to use the

chrome/browser/ui/views/frame/browser_non_client_frame_view.h

Index: chrome/browser/ui/views/frame/browser_non_client_frame_view.h
diff --git a/chrome/browser/ui/views/frame/browser_non_client_frame_view.h b/chrome/browser/ui/views/frame/browser_non_client_frame_view.h
index 681a06e7a447f457f0470ea25f157272e3302bef..a190aa8911f043b3b2f40ea1c09e98d2e793c9cd 100644
--- a/chrome/browser/ui/views/frame/browser_non_client_frame_view.h
+++ b/chrome/browser/ui/views/frame/browser_non_client_frame_view.h
@@ -59,6 +59,10 @@ class BrowserNonClientFrameView : public views::NonClientFrameView {
                                  bool is_visible) OVERRIDE;
   virtual void OnThemeChanged() OVERRIDE;
 
+  // Anchor and show the ProfileChooser bubble under the avatar button in
+  // the caption area.
+  void ShowProfileChooserViewBubble();

[sky, 2013/11/05 15:56:12]

On second thought. I think you should move this to BrowserView and expose the
new_avatar_button.

+
  protected:
   BrowserView* browser_view() const { return browser_view_; }
   BrowserFrame* frame() const { return frame_; }
@@ -72,10 +76,6 @@ class BrowserNonClientFrameView : public views::NonClientFrameView {
   void UpdateNewStyleAvatarInfo(views::ButtonListener* listener,
                                 const NewAvatarButton::AvatarButtonStyle style);
 
-  // Anchor and show the ProfileChooser bubble under the avatar button in
-  // the caption area.
-  void ShowProfileChooserViewBubble();
-
  private:
   // The frame that hosts this view.
   BrowserFrame* frame_;