Plumb requireInteraction to PlatformNotificationData & database

chrome/browser/notifications/platform_notification_service_impl.cc

Index: chrome/browser/notifications/platform_notification_service_impl.cc
diff --git a/chrome/browser/notifications/platform_notification_service_impl.cc b/chrome/browser/notifications/platform_notification_service_impl.cc
index 560fa06a4895842b35789cd800836a542d8ee8fb..60f432f35cd100803dd3eb457fbe1cb846291709 100644
--- a/chrome/browser/notifications/platform_notification_service_impl.cc
+++ b/chrome/browser/notifications/platform_notification_service_impl.cc
@@ -343,8 +343,11 @@ Notification PlatformNotificationServiceImpl::CreateNotificationFromData(
 
   notification.set_buttons(buttons);
 
-  // Web Notifications do not timeout.
-  notification.set_never_timeout(true);
+  // On desktop, notifications with require_interaction==true stay on-screen
+  // rather than minimizing to the notification center after a timeout.
+  // On mobile, this is ignored (notifications are minimized at all times).
+  if (notification_data.require_interaction)

[Peter Beverloo, 2015/08/28 14:17:54]

We can't do this.

The feature is still marked as experimental and thus not enabled by default.
This means that the default behavior in Chromium builds (and soon Canary/Dev)
will change to auto-minimize, with no means for developers to change this
behavior.

I'm not sure what the right course of action here is. Check for the
experimental-web-platform-features command line flag?

+    notification.set_never_timeout(true);
 
   return notification;
 }