Lazy creating of background pages --enable-lazy-background-pages)

chrome/common/chrome_switches.cc

 // 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.
 
 #include "chrome/common/chrome_switches.h"
 
 #include "base/base_switches.h"
 #include "base/command_line.h"
 
 namespace switches {
@@ skipping 431 matching lines @@
 const char kEnableIPv6[]                    = "enable-ipv6";
 
 /// Enable the IPC fuzzer for reliability testing
 const char kEnableIPCFuzzing[]               = "enable-ipc-fuzzing";
 
 // Enables IP Pooling within the networks stack (SPDY only).  When a connection
 // is needed for a domain which shares an IP with an existing connection,
 // attempt to use the existing connection.
 const char kEnableIPPooling[]               = "enable-ip-pooling";
 
+// Enables some extension background pages to be loaded when they are
+// needed rather than when the extensions are first loaded.
+const char kEnableLazyBackgroundPages[]     = "lazy-background-pages";

[Aaron Boodman, 2011/08/17 04:24:15]

The flag name should follow the convention of the others, so
--enable-lazy-background-pages.

[Tessa MacDuff, 2011/08/18 16:58:10]

Done.

+
 // Enables MAC cookies in the network stack.  These cookies use HMAC to
 // protect session state from passive network attackers.
 // http://tools.ietf.org/html/draft-hammer-oauth-v2-mac-token
 const char kEnableMacCookies[]              = "enable-mac-cookies";
 
 // Allows reporting memory info (JS heap size) to page.
 const char kEnableMemoryInfo[]              = "enable-memory-info";
 
 // Runs the Native Client inside the renderer process and enables GPU plugin
 // (internally adds lEnableGpuPlugin to the command line).
@@ skipping 769 matching lines @@
 
 // -----------------------------------------------------------------------------
 // DO NOT ADD YOUR CRAP TO THE BOTTOM OF THIS FILE.
 //
 // You were going to just dump your switches here, weren't you? Instead,
 // please put them in alphabetical order above, or in order inside the
 // appropriate ifdef at the bottom. The order should match the header.
 // -----------------------------------------------------------------------------
 
 }  // namespace switches