Linux native notifications: Support infinite timeouts

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 7ac30813b4724bad95f5389133e8a146b174caa1..79ae1651465dda83865f2b41dd0974b01ced8478 100644
--- a/chrome/browser/notifications/notification_platform_bridge_linux.cc
+++ b/chrome/browser/notifications/notification_platform_bridge_linux.cc
@@ -535,7 +535,9 @@ class NotificationPlatformBridgeLinuxImpl
     writer.CloseContainer(&hints_writer);
 
     const int32_t kExpireTimeoutDefault = -1;

[Peter Beverloo, 2017/05/09 22:52:08]

qq: is there any way to know what the default timeout is? we timed ~25 seconds
as being ideal for transient notifications a bunch of years ago.

[Tom (Use chromium acct), 2017/05/10 21:20:58]

There's no way to know :(  We could set the timeout to be 25000, but I think
that would confuse/annoy some % of users, so I'd opt to keep it at the default.

-    writer.AppendInt32(kExpireTimeoutDefault);
+    const int32_t kExpireTimeoutNever = 0;
+    writer.AppendInt32(notification->never_timeout() ? kExpireTimeoutNever
+                                                     : kExpireTimeoutDefault);
 
     std::unique_ptr<dbus::Response> response =
         notification_proxy_->CallMethodAndBlock(