Fix some infobar problems.

chrome/browser/ui/cocoa/infobars/infobar_container_controller.mm

Index: chrome/browser/ui/cocoa/infobars/infobar_container_controller.mm
diff --git a/chrome/browser/ui/cocoa/infobars/infobar_container_controller.mm b/chrome/browser/ui/cocoa/infobars/infobar_container_controller.mm
index 4e5df309324a4ed1e5d295403d12da23d8247fb5..f61429ea31361904b2c5f226ccc2d0c66fb64b5f 100644
--- a/chrome/browser/ui/cocoa/infobars/infobar_container_controller.mm
+++ b/chrome/browser/ui/cocoa/infobars/infobar_container_controller.mm
@@ -160,4 +160,12 @@
   [infobarControllers_ removeObject:controller];
 }
 
+- (void)setMaxTopArrowHeight:(NSInteger)height {
+  containerCocoa_->SetMaxTopArrowHeight(height);
+}
+
+- (NSInteger)defaultArrowHeight {
+  return infobars::InfoBar::kDefaultArrowTargetHeight;

[Malcolm, 2014/08/08 10:51:51]

I prefer not to expose the infobars namespace out of the InfoBarController,
will break encapsulation.

[Robert Sesek, 2014/08/08 14:32:31]

Why do you think it breaks encapsulation? By having this be a method instead of
just using a constant, it requires understanding that this always returns a
constant value, rather than a variable one.

[Malcolm, 2014/08/08 15:54:25]

Sounds reasonable. From my point of view, InfoBarContainerController should have
all necessary interfaces. If including infobar_container_controller.h AND
infobar_cocoa.h at the same time, I'll feel a little confused, because
InfoBarCocoa is not a controller/view. 

+}
+
 @end