Introduce a new API to handle native notification clicks

chrome/browser/notifications/message_center_display_service.cc

Index: chrome/browser/notifications/message_center_display_service.cc
diff --git a/chrome/browser/notifications/message_center_display_service.cc b/chrome/browser/notifications/message_center_display_service.cc
index 8dc7420cafe2b9fdc9811c8ff68980b7a12b6de2..f97e54a2dfa5ec28bbaa9378e9afc250598dff81 100644
--- a/chrome/browser/notifications/message_center_display_service.cc
+++ b/chrome/browser/notifications/message_center_display_service.cc
@@ -15,12 +15,16 @@ MessageCenterDisplayService::MessageCenterDisplayService(
 
 MessageCenterDisplayService::~MessageCenterDisplayService() {}
 
-void MessageCenterDisplayService::Display(const std::string& notification_id,
-                                          const Notification& notification) {
+void MessageCenterDisplayService::Display(
+    NotificationCommon::Type notification_type,
+    const std::string& notification_id,
+    const Notification& notification) {
   ui_manager_->Add(notification, profile_);

[Peter Beverloo, 2016/07/05 14:25:33]

Maybe add a TODO saying that the MCDS should stop relying on the
|notification|'s delegate? Not feasible to do for now, though, until we move to
the mojom for |notification|.

[Miguel Garcia, 2016/07/05 17:12:51]

Done.

 }
 
-void MessageCenterDisplayService::Close(const std::string& notification_id) {
+void MessageCenterDisplayService::Close(
+    NotificationCommon::Type notification_type,
+    const std::string& notification_id) {
   ui_manager_->CancelById(notification_id,
                           NotificationUIManager::GetProfileID(profile_));
 }