Message center code is spread across ash/system/, ui/message_center/, chrome/browser/ui/views/message_center, and chrome/browser/ui/cocoa/notifications. It seems a lot of the structure is obsolete and can be simplified or moved to new locations, which will be a helpful precursor to mojofication.
Steven & Xiyuan, do you know if there are features under development for M61 that touch the message center?
I'm not aware of any, but I don't review code in that directory very often.
The Cocoa implementation will be removed in the next month or so.
It would be good to understand what direction you'd like to take it in. We want to create a more generic Notification service that also has the ability to defer to system notification centers on other platforms. (We'll continue using the message center on Windows and Linux for the foreseeable future.)
Specific to the message center, it would be interesting to figure out an appropriate API for Chrome OS vs. the other platforms, given that it's way more capable on the former.
re #3: right now my only real plan is to start removing unnecessary dependencies and moving code to where it's used/needed so that it will be clearer what might be exposed via mojo vs. what can go in a public/cpp directory.
Comment 1 by jamescook@chromium.org
, Aug 15 2017