Use MacViews for ContentSettingBubbles.

chrome/browser/ui/views/content_setting_bubble_contents.h

Index: chrome/browser/ui/views/content_setting_bubble_contents.h
diff --git a/chrome/browser/ui/views/content_setting_bubble_contents.h b/chrome/browser/ui/views/content_setting_bubble_contents.h
index e2dff9ab0daf41f28be9648ffa8c48b83db22138..78672fbf0cbf0f04d8d9250ec521cd7e99fe923d 100644
--- a/chrome/browser/ui/views/content_setting_bubble_contents.h
+++ b/chrome/browser/ui/views/content_setting_bubble_contents.h
@@ -60,6 +60,9 @@ class ContentSettingBubbleContents : public content::WebContentsObserver,
   void UpdateMenuLabel(content::MediaStreamType type,
                        const std::string& label);
 
+  // Temporary hack for MacViews. Do not use this.

[tapted, 2016/01/11 02:50:58]

I think if you declare ContentSettingBubbleBridge as a friend, you'll be able to
call SetAnchorRect directly which is a bit neater (and it's a common pattern for
a Bridge class to be a friend/inner-class of one of the things it's bridging).

But! of course... you can't do this if we go for a standalone function in
browser_dialogs.h, so I'll update the comment there. I think a friend is the
least intrusive approach, but c/b/ui/views owners may have a different opinion
(e.g. for some of the other dialogs, we overloaded the constructor)

I guess we could also declare a friend *function*, but that's not a common
practice in Chrome -- friend classes are easier to understand and nicer to
maintain.

+  void SetExplicitAnchorRect(const gfx::Rect& rect);
+
  protected:
   // views::BubbleDelegateView:
   void Init() override;