[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Changed in: ubuntu-ux Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages 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 Ubuntu UX: Fix Released Status in Unity: Invalid Status in unity-notifications: Confirmed Status in indicator-network package in Ubuntu: Fix Released Status in telephony-service package in Ubuntu: Triaged 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
** No longer affects: telephony-service (Ubuntu) ** Project changed: telephony-service = telephony-service (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages 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 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: Triaged 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Changed in: telephony-service Status: New = Triaged ** Changed in: telephony-service Importance: Undecided = Medium -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages 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: Triaged 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Changed in: telephony-service (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages 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: Triaged 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: Triaged 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Changed in: telephony-service (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages 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: Triaged 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: Triaged 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
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 DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
Re: [Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
Am 11.06.2014 12:20, schrieb Lars Uebernickel: 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. The hint x-canonical-snap-decisions is an indicating hint, e.g. like the standard body hint, and used to point out that there are certain rules enforced upon the use of actions, put forth by UX-design, which deviate from the FDO-standard. Therefore I do not regard x-canonical-snap-decisions as being unnecessary. Furthermore hints are the designated means to introduce new features (or different behaviour). It's unlikely that developers have a problem understanding that the timeout only applies to a specific kind of notification. Being explicit rather than implicit avoids misunderstanding and possible false-positive bug-reports due to that. Adding additional hints only increases the complexity of the API and makes it harder to switch between different kinds of notifications. By design every introduced notification-type serves a very specific purpose, that differs in behaviour, visuals and interaction. Thus switching between different notification-types is not a common thing to do for a developer, unless UX-requirements change later on. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
It's unlikely that developers have a problem understanding that the timeout only applies to a specific kind of notification. Being explicit rather than implicit avoids misunderstanding and possible false-positive bug-reports due to that. I agree with that sentiment, but think it's the wrong trade-off with regards to simplicity. We already have precedence for snap decisions behaving differently when using the standard API (for example, snap decisions must have at least one action and they're the only notification type that can be cancelled). Did we see many bug reports from confused developers for that? Adding additional hints only increases the complexity of the API and makes it harder to switch between different kinds of notifications. By design every introduced notification-type serves a very specific purpose, that differs in behaviour, visuals and interaction. Thus switching between different notification-types is not a common thing to do for a developer, unless UX-requirements change later on. UX requirements change all the time. Also, just because it's not common doesn't mean we need to make it difficult. I'll stop arguing about this though if you feel strongly about it. I don't think we'll be using this API for much longer anyway. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Changed in: indicator-network (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
Reopening, because adding the x-canonical-snap-decisions-timeout hint was a bad idea. The notification spec already has a timeout parameter on org.freedesktop.Notifications.Notify(). We can just use that one for snap decisions and ignore it for all other notification types. I've attached branches for unity-notifications and indicator-network. ** Changed in: unity-notifications Status: Fix Released = Confirmed ** Changed in: indicator-network (Ubuntu) Status: Fix Released = Confirmed ** Branch linked: lp:~larsu/unity-notifications/revert-timeout ** Branch linked: lp:~larsu/indicator-network/use-standard-timeout -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages 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: Confirmed 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
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. 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. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages 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: Confirmed 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Branch linked: lp:ubuntu/utopic-proposed/unity-notifications -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Network Menu: New Status in Ubuntu UX bugs: Fix Committed Status in Unity: Triaged Status in Server and client library for desktop notifications in Unity: In Progress Status in “indicator-network” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Confirmed Status in “unity-notifications” package in Ubuntu: Confirmed 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
This bug was fixed in the package indicator-network - 0.5.1+14.10.20140602-0ubuntu1 --- indicator-network (0.5.1+14.10.20140602-0ubuntu1) utopic; urgency=low [ CI bot ] * Resync trunk [ Antti Kaijanmäki ] * Use x-canonical-snap-decisions-timeout on the wifi password and sim unlock dialogs to prevent them from expiring automatically. (LP: #1295762) -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 02 Jun 2014 11:03:06 + ** Changed in: indicator-network (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Network Menu: New Status in Ubuntu UX bugs: Fix Committed Status in Unity: Triaged Status in Server and client library for desktop notifications in Unity: In Progress Status in “indicator-network” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Confirmed 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
This bug was fixed in the package unity-notifications - 0.1.1+14.10.20140602-0ubuntu1 --- unity-notifications (0.1.1+14.10.20140602-0ubuntu1) utopic; urgency=low [ Mirco Müller ] * Added a snap-decisions-specific hint to allow control over the timeout of a notification. (LP: #1295762) -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 02 Jun 2014 10:58:29 + ** Changed in: unity-notifications (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Network Menu: New Status in Ubuntu UX bugs: Fix Committed Status in Unity: Triaged Status in Server and client library for desktop notifications in Unity: In Progress Status in “indicator-network” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Confirmed 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
added telephony-service to affected projects as we still need the incoming call snap decision and some of the messaging snap decisions to use this hint. ** Also affects: telephony-service Importance: Undecided Status: New ** Changed in: telephony-service Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko) ** Changed in: indicator-network Status: New = Fix Released ** Changed in: unity-notifications Status: In Progress = Fix Released ** Changed in: unity Status: Triaged = Invalid ** Changed in: unity (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages 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: Fix Released Status in “indicator-network” package in Ubuntu: Fix Released 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
marked the Unity as Invalid as no changes needed on that side. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages 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: Fix Released Status in “indicator-network” package in Ubuntu: Fix Released 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Branch unlinked: lp:~unity-api-team/indicator-network/devel -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Network Menu: New Status in Ubuntu UX bugs: Fix Committed Status in Unity: Triaged Status in Server and client library for desktop notifications in Unity: In Progress Status in “indicator-network” package in Ubuntu: New Status in “unity” package in Ubuntu: Confirmed Status in “unity-notifications” package in Ubuntu: Confirmed 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Also affects: indicator-network Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Network Menu: New Status in Ubuntu UX bugs: Fix Committed Status in Unity: Triaged Status in Server and client library for desktop notifications in Unity: In Progress Status in “unity” package in Ubuntu: Confirmed Status in “unity-notifications” package in Ubuntu: Confirmed 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Branch linked: lp:~unity-api-team/indicator-network/devel -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Network Menu: New Status in Ubuntu UX bugs: Fix Committed Status in Unity: Triaged Status in Server and client library for desktop notifications in Unity: In Progress Status in “unity” package in Ubuntu: Confirmed Status in “unity-notifications” package in Ubuntu: Confirmed 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
If thee is a decision to be made, then the timeout should probably be infinite, unless the app wants it to time out explicitly. Otherwise, the use of the notification API feels a bit strange to me. Snap decisions feel like something different, which should have a snap decision API, where an application can express what the /decision/ is about. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Ubuntu UX bugs: Fix Committed Status in Unity: Triaged Status in Server and client library for desktop notifications in Unity: In Progress Status in “unity” package in Ubuntu: Confirmed Status in “unity-notifications” package in Ubuntu: Confirmed 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/ubuntu-ux/+bug/1295762/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Branch linked: lp:~macslow/unity-notifications/fix-1295762 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Ubuntu UX bugs: Fix Committed Status in Unity: Triaged Status in Server and client library for desktop notifications in Unity: In Progress Status in “unity” package in Ubuntu: Confirmed Status in “unity-notifications” package in Ubuntu: Confirmed 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/ubuntu-ux/+bug/1295762/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Changed in: unity-notifications Status: Triaged = In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Ubuntu UX bugs: Fix Committed Status in Unity: Triaged Status in Server and client library for desktop notifications in Unity: In Progress Status in “unity” package in Ubuntu: Confirmed Status in “unity-notifications” package in Ubuntu: Confirmed 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/ubuntu-ux/+bug/1295762/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Ubuntu UX bugs: Fix Committed Status in Unity: Triaged Status in Server and client library for desktop notifications in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Status in “unity-notifications” package in Ubuntu: Confirmed 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/ubuntu-ux/+bug/1295762/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-notifications (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Ubuntu UX bugs: Fix Committed Status in Unity: Triaged Status in Server and client library for desktop notifications in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Status in “unity-notifications” package in Ubuntu: Confirmed 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/ubuntu-ux/+bug/1295762/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Changed in: unity-notifications Assignee: (unassigned) = Mirco Müller (macslow) ** Changed in: unity Assignee: (unassigned) = Mirco Müller (macslow) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Ubuntu UX bugs: Fix Committed Status in Unity: Triaged Status in Server and client library for desktop notifications in Unity: Triaged Status in “unity” package in Ubuntu: New Status in “unity-notifications” package in Ubuntu: New 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/ubuntu-ux/+bug/1295762/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
As discussed with Olga last week, a possible solution would be the introduction of a new integer hint (e.g. x-canonical-private-timeout), which would allow a snap-decision to divert from the regular timeout- behaviour that's usually the case with snap-decisions. On could argue if we start using the the regular notify_notification_set_timeout() instead of a dedicated hint. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Ubuntu UX bugs: Fix Committed Status in Unity: Triaged Status in Server and client library for desktop notifications in Unity: Triaged Status in “unity” package in Ubuntu: New Status in “unity-notifications” package in Ubuntu: New 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/ubuntu-ux/+bug/1295762/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
