Fix some infobar problems.

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

 // Copyright (c) 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #import "chrome/browser/ui/cocoa/infobars/infobar_container_controller.h"
 
 #include "base/logging.h"
 #include "base/mac/mac_util.h"
 #include "chrome/browser/infobars/infobar_service.h"
 #import "chrome/browser/ui/cocoa/browser_window_controller.h"
@@ skipping 142 matching lines @@
     return;
 
   // This code can be executed while InfoBarController is still on the stack, so
   // we retain and autorelease the controller to prevent it from being
   // dealloc'ed too early.
   [[controller retain] autorelease];
   [[controller view] removeFromSuperview];
   [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