Integrate new MD update menu icons.

chrome/common/chrome_switches.cc

Index: chrome/common/chrome_switches.cc
diff --git a/chrome/common/chrome_switches.cc b/chrome/common/chrome_switches.cc
index 3a833f8880afc94325658918577290eaf49a2430..b9e7c02c7d36fcfed3752809b365d454d928c1b6 100644
--- a/chrome/common/chrome_switches.cc
+++ b/chrome/common/chrome_switches.cc
@@ -948,6 +948,9 @@ const char kSilentDebuggerExtensionAPI[]    = "silent-debugger-extension-api";
 // one wishes to use Chrome as an ash server.
 const char kSilentLaunch[]                  = "silent-launch";
 
+// Simulates that bad modules have been found
+const char kSimulateBadModules[]            = "simulate-bad-modules";

[Peter Kasting, 2016/05/11 19:16:46]

We try to avoid switches if possible.  When they are necessary. they should be
for short-term debugging and there should be a concrete plan on when they'll be
removed.

Do you really need to add this, or have you done sufficient local testing to be
satisfied?  If there's a need to test the icon chosen when there are bad
modules, can that be tested by a unittest or similar instead of a switch?

[kylix_rd, 2016/05/11 19:54:43]

I wasn't clear on the philosophy of adding switches. This can certainly be
removed prior to the final commit version.

+
 // Simulates that elevation is needed to recover upgrade channel.
 const char kSimulateElevatedRecovery[]      = "simulate-elevated-recovery";