> I disagree. The "x-canonical-snap-decisions-timeout" is intentionally used in > favour of the Freedesktop timeout feature, to indicate very clearly, that is > is only applicable to snap-decisions notifications.
I think that's unnecessary for the same reason I thought introducing hints for snap decision actions was unnecessary. It's unlikely that developers have a problem understanding that the timeout only applies to a specific kind of notification. They already need to know about the different kinds of notifications and what they can do with them. Adding additional hints only increases the complexity of the API and makes it harder to switch between different kinds of notifications. > Using the regular parameter of the Notify() method - and only applying it > snap-decisioin notifications - would be misleading, because the intention of > that timeout parameter is to be affecting all kinds of notifications. We already go against the intention of that parameter by ignoring it completely. In fact, we go against the freedesktop specification, which states that notification servers need to honor this parameter. -- You received this bug notification because you are a member of Unity API bugs, which is subscribed to Network Menu. https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Network Menu: Fix Released Status in Telephony Service: New Status in Ubuntu UX bugs: Fix Committed Status in Unity: Invalid Status in Server and client library for desktop notifications in Unity: Confirmed Status in “indicator-network” package in Ubuntu: Fix Released Status in “telephony-service” package in Ubuntu: New Status in “unity” package in Ubuntu: Invalid Status in “unity-notifications” package in Ubuntu: Fix Released Bug description: Problem: If user receives an SMS/call, snap decision for incoming SMS/call stays on screen for always only 60sec. and then disappears from screen (by default). There was no interaction from user. Possible solution: The snap decision should stay on screen for the amount of time the app asks it to, being always app dependant. A 60sec. time-out is too short due to use cases where an action from user is mandatory. Use case example: A class 1/2 SMS arrives after user triggered a USSD command from dialer. These type of SMS always requires a response from user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is too short because it can be missed and these type of SMS is NOT saved into the usual messages thread. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1295762/+subscriptions -- Mailing list: https://launchpad.net/~unity-api-bugs Post to : unity-api-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~unity-api-bugs More help : https://help.launchpad.net/ListHelp
