Support chrome.windows extension API events for browserless Panels.

chrome/browser/ui/panels/panel_cocoa.mm

Index: chrome/browser/ui/panels/panel_cocoa.mm
diff --git a/chrome/browser/ui/panels/panel_cocoa.mm b/chrome/browser/ui/panels/panel_cocoa.mm
index 6d64a4525114f17c103a54886a2e91f1e13be3c2..c323db6474f8ed3bb2a48909c4640b6fe950fdd2 100644
--- a/chrome/browser/ui/panels/panel_cocoa.mm
+++ b/chrome/browser/ui/panels/panel_cocoa.mm
@@ -51,6 +51,12 @@ bool PanelCocoa::isClosed() {
 void PanelCocoa::ShowPanel() {
   ShowPanelInactive();
   ActivatePanel();
+
+  // |-makeKeyAndOrderFront:| won't send |-windowDidBecomeKey:| until we
+  // return to the runloop. This causes extension tests that wait for the
+  // active status change notification to fail, so we send an active status
+  // notification here.
+  panel_->OnActiveStateChanged(true);

[Dmitry Titov, 2012/07/13 18:24:17]

oy. 
Can it be that the consumers of that call are/will assume that the window
already changed the status when it is called? If so, they can be broken.

Or, what if ActivatePanel actually starts to fail to activate a panel, but the
tests will succeed because we call OnActiveStateChanged directly here?

[jennb, 2012/07/13 18:47:48]

I had the same concerns, therefore I added the EXPECT_EQ in
test_panel_active_state_observer.cc to see if the state is actually changed even
though |-windowDidBecomeKey| has not been fired. All was happy.

 }
 
 void PanelCocoa::ShowPanelInactive() {