Rebase the MessageBubble on the new views bubble.

chrome/browser/ui/views/window.h

 // Copyright (c) 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef CHROME_BROWSER_UI_VIEWS_WINDOW_H_
 #define CHROME_BROWSER_UI_VIEWS_WINDOW_H_
 #pragma once
 
 #include "ui/gfx/native_widget_types.h"
 
@@ skipping 10 matching lines @@
                                  views::WidgetDelegate* delegate);
 
 // Create a bubble for a given |delegate|. Takes care of chromeos
 // specific window type setting if needed.
 views::Widget* CreateViewsBubble(views::BubbleDelegateView* delegate);
 
 // Create a bubble that will show even when chromeos screen is locked,
 // for a given |delegate|. Takes care of chromeos specific window
 // type setting. For bubbles that do not need to be shown when screen
 // 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_