[md] Give each infobar its own layer.

chrome/browser/ui/views/infobars/infobar_container_view.cc

Index: chrome/browser/ui/views/infobars/infobar_container_view.cc
diff --git a/chrome/browser/ui/views/infobars/infobar_container_view.cc b/chrome/browser/ui/views/infobars/infobar_container_view.cc
index 450d69f52c0eafff5892eb3d168fe1627f06021c..cc3f0f3a644789e6c464891495137ed4002fe29c 100644
--- a/chrome/browser/ui/views/infobars/infobar_container_view.cc
+++ b/chrome/browser/ui/views/infobars/infobar_container_view.cc
@@ -18,8 +18,6 @@ InfoBarContainerView::InfoBarContainerView(Delegate* delegate)
     : infobars::InfoBarContainer(delegate) {
   set_id(VIEW_ID_INFO_BAR_CONTAINER);
   SetEventTargeter(make_scoped_ptr(new views::ViewTargeter(this)));
-  SetPaintToLayer(true);
-  layer()->SetFillsBoundsOpaquely(false);
 }
 
 InfoBarContainerView::~InfoBarContainerView() {
@@ -73,5 +71,5 @@ bool InfoBarContainerView::DoesIntersectRect(const View* target,
   DCHECK_EQ(this, target);
   // Don't handle events on the vertical overlap portion of the view (the
   // vertical space occupied by the arrow).

[Peter Kasting, 2016/03/08 01:08:17]

Add to this comment to describe why we want to reject these.

[Evan Stade, 2016/03/08 01:43:29]

Done.

-  return rect.bottom() >= GetVerticalOverlap(nullptr);
+  return rect.CenterPoint().y() >= GetVerticalOverlap(nullptr);

[Peter Kasting, 2016/03/08 01:08:17]

Why did this have to be changed?

I'm getting increasingly uncomfortable with this inequality -- can we just do a
true intersection of the non-top-arrow part of the container view with the
supplied rect?

[Evan Stade, 2016/03/08 01:43:29]

It did not have to be part of this CL. It's somewhat tangential.

When you're using a mouse, it won't make a difference, which is why it seemed
right to me before. Now that I think more about it, it seems wrong because if
you are considering touch events, we probably want to check the middle of your
finger, not the bottom edge.

[tdanderson, 2016/03/14 17:53:03]

You should leave this as rect.bottom() (explained in my other comment).

 }