Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(803)

Unified Diff: chrome/browser/chrome_content_browser_client.cc

Issue 2381753002: Use mojo SystemTray interfaces for both mash and classic ash (Closed)
Patch Set: cleanup Created 4 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: chrome/browser/chrome_content_browser_client.cc
diff --git a/chrome/browser/chrome_content_browser_client.cc b/chrome/browser/chrome_content_browser_client.cc
index 7fe51b98a766693044495bfa3e3512dd4fe225e2..9675afd1f09711bae09d64be3ba02ad33d1bce3d 100644
--- a/chrome/browser/chrome_content_browser_client.cc
+++ b/chrome/browser/chrome_content_browser_client.cc
@@ -2990,6 +2990,8 @@ void ChromeContentBrowserClient::RegisterInProcessMojoApplications(
#endif
#if defined(OS_CHROMEOS)
if (chrome::IsRunningInMash()) {
sky 2016/09/29 16:34:05 I don't think there is a reason this needs to be c
+ // TODO - would need to register SystemTrayClient, even if not running in
+ // mash. I'm not sure how to do that.
content::MojoShellConnection::GetForProcess()->AddConnectionFilter(
base::MakeUnique<chromeos::ChromeInterfaceFactory>());
}

Powered by Google App Engine
This is Rietveld 408576698