From 7603d7f7d625bd27aa98fbdd28b8cff83344f66f Mon Sep 17 00:00:00 2001 From: "brettw@chromium.org" Date: Thu, 25 Mar 2010 19:15:37 +0000 Subject: Remove the disable metrics command line flag, which is no longer used for anything. This flag was leftover from initial product development when there was no opt-in preference for enabling the metrics service. The only user was a ChromeFrame unit test which I modified to use a different one that has the same effect. BUG=none TEST=none Review URL: http://codereview.chromium.org/1290004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42651 0039d316-1c4b-4281-b951-d872f2087c98 --- chrome_frame/chrome_launcher.cc | 1 - 1 file changed, 1 deletion(-) (limited to 'chrome_frame/chrome_launcher.cc') diff --git a/chrome_frame/chrome_launcher.cc b/chrome_frame/chrome_launcher.cc index 484c6de..d786010 100644 --- a/chrome_frame/chrome_launcher.cc +++ b/chrome_frame/chrome_launcher.cc @@ -22,7 +22,6 @@ const wchar_t kLauncherExeBaseName[] = L"chrome_launcher.exe"; const char* kAllowedSwitches[] = { switches::kAutomationClientChannelID, switches::kChromeFrame, - switches::kDisableMetrics, switches::kEnableRendererAccessibility, switches::kEnableExperimentalExtensionApis, switches::kNoErrorDialogs, -- cgit v1.1