Linux native notifications: Implement GetDisplayedNotifications

chrome/browser/notifications/notification_platform_bridge_linux.cc

Index: chrome/browser/notifications/notification_platform_bridge_linux.cc
diff --git a/chrome/browser/notifications/notification_platform_bridge_linux.cc b/chrome/browser/notifications/notification_platform_bridge_linux.cc
index cf71db8869d0a8a1c7c5f89085a7fd8338243d6c..38869b87da57e1c17c64e0c89586fa7c2b388512 100644
--- a/chrome/browser/notifications/notification_platform_bridge_linux.cc
+++ b/chrome/browser/notifications/notification_platform_bridge_linux.cc
@@ -454,10 +454,14 @@ class NotificationPlatformBridgeLinuxImpl
       bool incognito,
       const GetDisplayedNotificationsCallback& callback) const {
     DCHECK(task_runner_->RunsTasksOnCurrentThread());
-    // TODO(thomasanderson): Implement.
-    PostTaskToUiThread(base::BindOnce(
-        callback, base::Passed(base::MakeUnique<std::set<std::string>>()),
-        false));
+    auto displayed = base::MakeUnique<std::set<std::string>>();
+    for (const auto& notification : notifications_) {
+      if (notification.first->profile_id == profile_id &&
+          notification.first->is_incognito == incognito) {
+        displayed->insert(notification.first->notification_id);
+      }
+    }

[Peter Beverloo, 2017/05/02 13:53:42]

Are we confident that we can rely on the NotificationClosed signal for all
cases? (User dismisses the notification, we dismiss the notification, it
expires, etcetera?) The docs look good, but just to make sure.

These seem like excellent cases to add tests for by the way.

[Tom (Use chromium acct), 2017/05/02 20:59:16]

yes I believe so

+    PostTaskToUiThread(base::BindOnce(callback, std::move(displayed), true));
   }
 
   NotificationData* FindNotificationData(const std::string& notification_id,