Rebase the MessageBubble on the new views bubble.

chrome/browser/ui/views/window.h

Index: chrome/browser/ui/views/window.h
diff --git a/chrome/browser/ui/views/window.h b/chrome/browser/ui/views/window.h
index d5b5a5a3f71fa13c46ad807e26fe5e9e95cd0d67..4b4709ab4b118157e845d44fe229e60fd1a712b4 100644
--- a/chrome/browser/ui/views/window.h
+++ b/chrome/browser/ui/views/window.h
@@ -30,6 +30,7 @@ views::Widget* CreateViewsBubble(views::BubbleDelegateView* delegate);
 // is locked, use CreateViewsBubble instead.
 views::Widget* CreateViewsBubbleAboveLockScreen(

[Nikita (slow), 2011/11/29 13:08:37]

In general I don't think that every bubble should be created on top of lock
screen. Only those that are created from the lock screen should be placed so.
But you may fix that in upcoming CL if that's needed.

[msw, 2011/11/29 19:49:52]

Most bubbles use |CreateViewsBubble|, not |CreateViewsBubbleAboveLockScreen|.
MessageBubble is an exception for it's password errors shown on
ScreenLockerViews. Once that's deprecated in favor of the WebUIScreenLocker, the
3G Promo will be the only MessageBubble, and that should warrant some extra
cleanup. More generally, this isn't needed for aura and should eventually be
deprecated along with the legacy WM IPC code it uses. For the time being,
however, this seems unavoidable.

     views::BubbleDelegateView* delegate);
+
 }  // namespace browser
 
 #endif  // CHROME_BROWSER_UI_VIEWS_WINDOW_H_