This MP switches the notification from a Snap to Interactive; however, it regresses on bug #1324580 in that the notification times out quickly, ignoring the duration suggested by ubuntu-clock-app.
This may be by design for Interactive notifications in unity- notifications, as NotificationServer::buildNotification() doesn't use the timeout hint in Interactive mode. Indeed, the timeout hint's key is "x-canonical-snap-decisions-timeout" The simplest way to satisfy both tickets would be to add a couple of lines to NotificationServer::buildNotification() so timeouts aren't limited to snap decisions. I don't know if/how that affects other design constraints in unity-notifications... adding MacSlow to the ticket for another opinion. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1350426 Title: Alarm notification should be changed to an interactive notification Status in Clock application for Ubuntu devices: In Progress Status in Server and client library for desktop notifications in Unity: New Status in “indicator-datetime” package in Ubuntu: In Progress Bug description: As per the latest design spec, the snap notification that is shown when an alarm is triggered will be replaced with a interactive notification. The design spec for the interactive notification is shown at [1]. Please ensure that the strings shown in the spec are translatable. The timing of how long the notification should be shown are similar to the snap notification behavior we have atm. https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1350426/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
