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

Unified Diff: chrome/app/mojo/chrome_manifest.json

Issue 2381753002: Use mojo SystemTray interfaces for both mash and classic ash (Closed)
Patch Set: Restructure based on feedback 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/app/mojo/chrome_manifest.json
diff --git a/chrome/app/mojo/chrome_manifest.json b/chrome/app/mojo/chrome_manifest.json
index 3abfa8540aa0e1dd74c36989c84c4b754f307b0c..b6f405f21759a9a0f97eb1293bb643b30f008302 100644
--- a/chrome/app/mojo/chrome_manifest.json
+++ b/chrome/app/mojo/chrome_manifest.json
@@ -16,6 +16,13 @@
"interfaces": [ "ash::autoclick::mojom::AutoclickController" ]
}
},
- "provided": { "mash:launchable": [ "mash::mojom::Launchable" ] }
+ "provided": {
+ "mash:launchable": [
+ "mash::mojom::Launchable"
+ ],
+ "ash": [
msw 2016/09/30 23:26:49 It might be nice to avoid using classes; but maybe
James Cook 2016/10/03 18:07:56 Me too, but rockot recommended I do it this way. (
msw 2016/10/03 19:04:43 No, you don't *need* to put provided interfaces in
James Cook 2016/10/03 20:15:00 rockot, thoughts?
+ "ash::mojom::SystemTrayClient"
+ ]
+ }
}
}

Powered by Google App Engine
This is Rietveld 408576698