| commit | 2ccf45c50fad0f2c3c20d95eef6d0040b565b291 | [log] [tgz] |
|---|---|---|
| author | [email protected] <[email protected]@0039d316-1c4b-4281-b951-d872f2087c98> | Fri Aug 19 23:35:50 2011 |
| committer | [email protected] <[email protected]@0039d316-1c4b-4281-b951-d872f2087c98> | Fri Aug 19 23:35:50 2011 |
| tree | 73eac41769a4678fcdb566e78d6e3bde7c10617c | |
| parent | da930e1b7adfb28f6895d95004c25984af627080 [diff] [blame] |
Prefix all IPC messages used by src\chrome with Chrome. For e.g ChromeViewMsg_, ChromeViewHostMsg, etc. This makes it easier to identify which messages are specific to content and chrome. This is a preparation CL for bug http://code.google.com/p/chromium/issues/detail?id=87335 which requires IPC's to not span across content and chrome. When IPC's cross these boundaries they need to be handled as API calls. BUG=87335 Review URL: http://codereview.chromium.org/7631063 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@97536 0039d316-1c4b-4281-b951-d872f2087c98
diff --git a/chrome/browser/chrome_content_browser_client.cc b/chrome/browser/chrome_content_browser_client.cc index e89776d..8c6aeaf4 100644 --- a/chrome/browser/chrome_content_browser_client.cc +++ b/chrome/browser/chrome_content_browser_client.cc
@@ -121,7 +121,8 @@ host->channel()->AddFilter(new TextInputClientMessageFilter(host->id())); #endif - host->Send(new ViewMsg_SetIsIncognitoProcess(profile->IsOffTheRecord())); + host->Send(new ChromeViewMsg_SetIsIncognitoProcess( + profile->IsOffTheRecord())); } void ChromeContentBrowserClient::PluginProcessHostCreated(