Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 1 // Copyright 2017 The Chromium Authors. All rights reserved. | |
| 2 // Use of this source code is governed by a BSD-style license that can be | |
| 3 // found in the LICENSE file. | |
| 4 | |
| 5 #include "chrome/browser/extensions/api/notifications/extension_notification_han dler.h" | |
| 6 | |
| 7 #include "base/logging.h" | |
| 8 | |
| 9 ExtensionNotificationHandler::ExtensionNotificationHandler() = default; | |
| 10 | |
| 11 ExtensionNotificationHandler::~ExtensionNotificationHandler() = default; | |
| 12 | |
| 13 void ExtensionNotificationHandler::OnClose(Profile* profile, | |
| 14 const std::string& origin, | |
| 15 const std::string& notification_id, | |
| 16 bool by_user) { | |
| 17 // TODO(peter): Call EraseDataForNotificationId from here once this event | |
|
Miguel Garcia
2017/02/21 10:56:43
Why would you not call it though? native NDSes wil
Peter Beverloo
2017/02/21 17:23:50
Because we'd end up clearing the data multiple tim
| |
| 18 // can be relied upon. (It's only been implemented for native NDSes.) | |
| 19 } | |
| 20 | |
| 21 void ExtensionNotificationHandler::OnClick( | |
|
Miguel Garcia
2017/02/21 10:56:43
So you are not propagating click/close events back
Peter Beverloo
2017/02/21 17:23:50
No. Same answer - we can't rely on this functional
| |
| 22 Profile* profile, | |
| 23 const std::string& origin, | |
| 24 const std::string& notification_id, | |
| 25 int action_index, | |
| 26 const base::NullableString16& reply) {} | |
| 27 | |
| 28 void ExtensionNotificationHandler::OpenSettings(Profile* profile) { | |
| 29 // Extension notifications don't display a settings button. | |
| 30 NOTREACHED(); | |
| 31 } | |
| 32 | |
| 33 void ExtensionNotificationHandler::RegisterNotification( | |
| 34 const std::string& notification_id, | |
| 35 NotificationDelegate* delegate) {} | |
| OLD | NEW |