Don't order the bubble window front; it shows up just fine.

chrome/browser/cocoa/status_bubble_mac.mm

 // Copyright (c) 2009 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.
 
 #include "chrome/browser/cocoa/status_bubble_mac.h"
 
 #include "base/string_util.h"
 #include "base/sys_string_conversions.h"
 #include "chrome/common/gfx/text_elider.h"
 #include "googleurl/src/gurl.h"
@@ skipping 195 matching lines @@
   [window_ setOpaque:NO];
   [window_ setHasShadow:NO];
 
   StatusBubbleViewCocoa* view =
       [[[StatusBubbleViewCocoa alloc] initWithFrame:NSZeroRect] autorelease];
   [window_ setContentView:view];
 
   [parent_ addChildWindow:window_ ordered:NSWindowAbove];
 
   [window_ setAlphaValue:0.0f];
-  [window_ orderFront:nil];

[Scott Hess - ex-Googler, 2009/04/01 00:36:39]

I noticed this with the omnibox things, too.  I don't understand child/parent
windows :-).  Anyhow, does this change imply you want to move the
-setAlpheValue: call above the -addChildWindow:ordered: call?  The old code
looks like it thinks that that is set before the window becomes visible.

[Avi (use Gerrit), 2009/04/01 00:48:06]

That might be a good idea, but for now this seems to work OK. If it turns out to
be flashing, I'll do that change.

 
   offset_ = 0;
   [view setStyle:STYLE_STANDARD];
   MouseMoved();
 }
 
 void StatusBubbleMac::FadeIn() {
   [NSAnimationContext beginGrouping];
   [[NSAnimationContext currentContext] setDuration:kShowFadeDuration];
   [[window_ animator] setAlphaValue:1.0f];
@@ skipping 90 matching lines @@
 
   NSDictionary* textDict = [NSDictionary dictionaryWithObjectsAndKeys:
     textFont, NSFontAttributeName,
     textShadow, NSShadowAttributeName,
     nil];
   [content_ drawAtPoint:NSMakePoint(kTextPositionX, kTextPositionY)
          withAttributes:textDict];
 }
 
 @end