dx-packages team mailing list archive

[David Barth <david.barth@xxxxxxxxxxxxx>]

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