Disable info bar animations during automated testing.

components/infobars/core/infobar_manager.cc

 // Copyright 2014 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.
 
 #include "components/infobars/core/infobar_manager.h"
 
 #include <utility>
 
 #include "base/command_line.h"
 #include "components/infobars/core/infobar.h"
@@ skipping 83 matching lines @@
 
 void InfoBarManager::AddObserver(Observer* obs) {
   observer_list_.AddObserver(obs);
 }
 
 void InfoBarManager::RemoveObserver(Observer* obs) {
   observer_list_.RemoveObserver(obs);
 }
 
 InfoBarManager::InfoBarManager()
-    : infobars_enabled_(true) {
+    : infobars_enabled_(true), animations_enabled_(true) {

[Peter Kasting, 2017/02/23 00:33:56]

Nit: You're welcome to move these initializations to the member declaration
points in the header if you want.

[samuong, 2017/02/23 00:45:26]

Done. Just to confirm, you meant using brace-initialization?

[Peter Kasting, 2017/02/23 00:51:34]

I would use "= true" in preference to "{true}", since AFAIK both are legal, and
that's what Chromium prefers in such cases:
https://www.chromium.org/developers/coding-style/cpp-dos-and-donts#TOC-Variab...

   if (base::CommandLine::ForCurrentProcess()->HasSwitch(
           switches::kDisableInfoBars))
     infobars_enabled_ = false;
 }
 
 InfoBarManager::~InfoBarManager() {}
 
 void InfoBarManager::ShutDown() {
   // Destroy all remaining InfoBars.  It's important to not animate here so that
   // we guarantee that we'll delete all delegates before we do anything else.
@@ skipping 39 matching lines @@
   infobars_.erase(i);
 
   // This notification must happen before the call to CloseSoon() below, since
   // observers may want to access |infobar| and that call can delete it.
   NotifyInfoBarRemoved(infobar, animate);
 
   infobar->CloseSoon();
 }
 
 }  // namespace infobars