Restore the iframe behavior of notification permissions

chrome/browser/notifications/desktop_notification_service.cc

Index: chrome/browser/notifications/desktop_notification_service.cc
diff --git a/chrome/browser/notifications/desktop_notification_service.cc b/chrome/browser/notifications/desktop_notification_service.cc
index eb6d72f6b7a30377eba03195accebb1370a8bd0e..3d58c11bc0f5fce6dbc0d675a1beafbebae2d60c 100644
--- a/chrome/browser/notifications/desktop_notification_service.cc
+++ b/chrome/browser/notifications/desktop_notification_service.cc
@@ -313,6 +313,23 @@ void DesktopNotificationService::OnExtensionUninstalled(
 #endif
 }
 
+// Unlike other permission types, granting a notification for a given origin
+// will not take into account the |embedder_origin|, it will only be based
+// on the requesting iframe origin.
+// TODO(mukai) Consider why notifications behave differently than
+// other permissions. crbug.com/416894
+void DesktopNotificationService::UpdateContentSetting(
+    const GURL& requesting_origin,
+    const GURL& embedder_origin,
+    bool allowed) {
+  if (allowed) {
+    DesktopNotificationProfileUtil::GrantPermission(
+        profile_, requesting_origin);
+  } else {
+    DesktopNotificationProfileUtil::DenyPermission(profile_, requesting_origin);
+  }
+}
+
 void DesktopNotificationService::OnNotificationPermissionRequested(
     const NotificationPermissionCallback& callback, bool allowed) {
   blink::WebNotificationPermission permission = allowed ?