Mac: Let browser_tests run in bundled mode for their whole lifetime.

chrome/common/pepper_plugin_registry.cc

 // Copyright (c) 2010 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 "chrome/common/pepper_plugin_registry.h"
 
 #include "base/command_line.h"
 #include "base/file_util.h"
 #include "base/native_library.h"
 #include "base/path_service.h"
@@ skipping 135 matching lines @@
 void PepperPluginRegistry::GetInternalPluginInfo(
     InternalPluginInfoList* plugin_info) {
   // Currently, to centralize the internal plugin registration logic, we
   // hardcode the list of plugins, mimetypes, and registration information
   // in this function.  This is gross, but because the GetList() function is
   // called from both the renderer and browser the other option is to force a
   // special register function for each plugin to be called by both
   // RendererMain() and BrowserMain().  This seemed like the better tradeoff.
   //
   // TODO(ajwong): Think up a better way to maintain the plugin registration
-  // information. Pehraps by construction of a singly linked list of
+  // information. Perhaps by construction of a singly linked list of
   // plugin initializers that is built with static initializers?
 
 #if defined(ENABLE_REMOTING)
   if (CommandLine::ForCurrentProcess()->HasSwitch(
       switches::kEnableRemoting)) {
     InternalPluginInfo info;
     // Add the chromoting plugin.
     DCHECK(info.is_internal);
     info.path =
         FilePath(FILE_PATH_LITERAL("internal-chromoting"));
@@ skipping 62 matching lines @@
     const FilePath& path = plugins[i].path;
     ModuleHandle module = pepper::PluginModule::CreateModule(path);
     if (!module) {
       DLOG(ERROR) << "Failed to load pepper module: " << path.value();
       continue;
     }
     module->set_name(plugins[i].name);
     modules_[path] = module;
   }
 }