Fix relaunches on the Mac

chrome/common/chrome_switches.h

Index: chrome/common/chrome_switches.h
===================================================================
--- chrome/common/chrome_switches.h	(revision 90037)
+++ chrome/common/chrome_switches.h	(working copy)
@@ -23,7 +23,6 @@
 
 // All switches in alphabetical order. The switches should be documented
 // alongside the definition of their values in the .cc file.
-extern const char kActivateOnLaunch[];

[Robert Sesek, 2011/06/23 19:30:16]

Yay! How does this affect launching normally from the command line?

[Mark Mentovai, 2011/06/23 20:23:03]

rsesek wrote:
It doesn’t affect it at all. Chrome still doesn’t activate, just like how it
didn’t activate before unless --activate was specified. Same for any other
application, for that matter.

(You don’t actually want to keep --activate around just for that, do you? If you
want activation, use “open.”)

[Robert Sesek, 2011/06/24 14:30:28]

No, I just imagine some users complaining and wanted to have a concrete answer.

 extern const char kAllowCrossOriginAuthPrompt[];
 extern const char kAllowFileAccess[];
 extern const char kAllowOutdatedPlugins[];
@@ -316,6 +315,7 @@
 
 #if defined(OS_MACOSX)
 extern const char kEnableExposeForTabs[];
+extern const char kRelauncherProcess[];
 #endif
 
 #if !defined(OS_MACOSX)