Closed
Bug 875586
Opened 11 years ago
Closed 10 years ago
Alarm notifications should use a stronger time approximation in the form of weeks, days, hours, minutes, and seconds
Categories
(Firefox OS Graveyard :: Gaia::Calendar, defect)
Tracking
(b2g18?, b2g-v1.2 affected, b2g-v1.3T affected, b2g-v1.4 affected)
RESOLVED
DUPLICATE
of bug 987427
People
(Reporter: jsmith, Unassigned)
References
Details
(Whiteboard: permafail)
See related bugs in bug 856881 and bug 875550. Right now, our alarm notifications in the calendar app appear to do the following calculation to indicate how much time is left before the event happens: - 4.55 minutes ==> 4 minutes (truncate) - 1.95 hours ==> 1 hours (truncate) - etc. For being off by a minute, this is minor. But the hour, day, and week cases are far worse - truncation causes us to confuse the user into thinking the wrong time by a lot. What we should do here is give a better approximation of how much time is remaining until the event happens. At one extreme, that would require indicating the following: - Weeks - Days - Hours - Minutes - Seconds This needs UX input though on what the right balance here is.
Reporter | ||
Updated•11 years ago
|
Summary: Alarm notifications should be use stronger time approximation in the form of weeks, days, hours, minutes, and seconds → Alarm notifications should use a stronger time approximation in the form of weeks, days, hours, minutes, and seconds
Reporter | ||
Comment 3•11 years ago
|
||
Need info on UX to determine what the right path forward is here.
tracking-b2g18:
--- → ?
Flags: needinfo?(firefoxos-ux-bugzilla)
Comment 4•11 years ago
|
||
UX will address this after completing leo+, tef+ and tracking-b2g18+ bugs, which are the top UX priorities right now.
Updated•11 years ago
|
Flags: needinfo?(firefoxos-ux-bugzilla) → needinfo?(rmacdonald)
Comment 5•11 years ago
|
||
The spec for this is available at: https://mozilla.box.com/files/0/f/867803710/1/f_8935133431
Flags: needinfo?(rmacdonald)
Comment 6•11 years ago
|
||
This bug also reproduces on the 10/25/13 1.2 build. Environmental Variables: Device: Buri v1.2 comRIL BuildID: 20131025004000 Gaia: 606517ceafe0950c2b89822d5f13353743334f2c Gecko: 5eabd267ef04 Version: 26.0a2 RIL Version: 01.02.00.019.082
status-b2g-v1.2:
--- → affected
Whiteboard: burirun3
Updated•10 years ago
|
Whiteboard: burirun3 → burirun3, burirun1.3-2
Updated•10 years ago
|
Whiteboard: burirun3, burirun1.3-2 → burirun3, burirun1.3-2, burirun1.3-3
Updated•10 years ago
|
Whiteboard: burirun3, burirun1.3-2, burirun1.3-3 → permafail
Updated•10 years ago
|
status-b2g-v1.4:
--- → affected
Updated•10 years ago
|
status-b2g-v1.3T:
--- → affected
Comment 7•10 years ago
|
||
Hi Kevin any update about this issue. when we set remind me is 5 minute before then event start after 4 minute came in notification.it should be 5 minute.
Flags: needinfo?(kgrandon)
Comment 8•10 years ago
|
||
Miller - I recall you looking at millisecond calculation for notifications. I couldn't find anything open, if you are doing anything can you update this bug? Thanks!
Flags: needinfo?(kgrandon) → needinfo?(mmedeiros)
Comment 9•10 years ago
|
||
Hi Kevin, it was Bug 987427 (related to notification rounding)
Flags: needinfo?(mmedeiros)
See Also: → 987427
Comment 10•10 years ago
|
||
I am assuming that the issue is a dupe of bug 987427. Generally I would dupe the other way, but given that the other bug has a patch and people working on it, I think we should dupe this way.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Comment 11•10 years ago
|
||
I think Dylan had some ideas on what we should do instead. I think he mentioned something about just showing the event date (since we don't update the value after the alarm fires of).
You need to log in
before you can comment on or make changes to this bug.
Description
•