Do not show permission bubble when browser is not active

chrome/browser/ui/views/frame/browser_view.cc

Index: chrome/browser/ui/views/frame/browser_view.cc
diff --git a/chrome/browser/ui/views/frame/browser_view.cc b/chrome/browser/ui/views/frame/browser_view.cc
index b39783fb509d5e73454ee3f535cc97c7b86c0154..382bee4282ec8c318446f8806cd80f12b60127ba 100644
--- a/chrome/browser/ui/views/frame/browser_view.cc
+++ b/chrome/browser/ui/views/frame/browser_view.cc
@@ -1821,6 +1821,16 @@ void BrowserView::OnWidgetDestroying(views::Widget* widget) {
     delete content;
 }
 
+void BrowserView::OnWidgetVisibilityChanged(views::Widget* widget,

[sky, 2017/03/27 15:47:51]

I think this logic belongs closer to the permissions code rather than
BrowserView. I think the permissions should be the one determining if the
browser containing the webcontents is the active browser, and it not install a
BrowserListObserver. Once the browser is active *and* the webcontents is active
then show the bubble.

[Qiang(Joe) Xu, 2017/03/27 21:09:52]

Yeah, I agree. And checking activation instead of visibility seems more
reasonable. It also covers more cases, like a permission bubble is scheduled but
another browser is created and set as active. 

+                                            bool visible) {
+  DCHECK_EQ(GetWidget(), widget);
+  if (widget->IsClosed() || !GetActiveWebContents())
+    return;
+
+  PermissionRequestManager::FromWebContents(GetActiveWebContents())
+      ->OnBrowserVisibilityChanged(visible);
+}
+
 void BrowserView::OnWidgetActivationChanged(views::Widget* widget,
                                             bool active) {
   if (active)