Closed Bug 810754 Opened 13 years ago Closed 12 years ago

[Notifications] Should appear w/ time stamps when displayed in Utility Tray and Lock screen

Categories

(Firefox OS Graveyard :: Gaia::System, defect, P1)

x86
macOS
defect

Tracking

(blocking-basecamp:+)

RESOLVED FIXED
B2G C2 (20nov-10dec)
blocking-basecamp +

People

(Reporter: jcarpenter, Assigned: mbudzynski)

References

Details

(Keywords: feature)

Attachments

(1 file)

When notifications are viewed on either the Lock screen or Utility tray they should be appended w/ time stamps in the upper right corner of the notification box. As per visual design specs: https://www.dropbox.com/sh/9xxxcxiflo3qpsb/ValHjcgEfW Incomplete feature work, nom'ing as blocking+. This is an important part of the utility of notifications.
What happens for notifications more than a day old?
Good question. Displaying total hours would not be of much value. We should instead switch to simplified dates such as "1 day ago". Don't we use PrettyDate elsewhere in the UX?
(In reply to Josh Carpenter [:jcarpenter] from comment #2) > Good question. Displaying total hours would not be of much value. We should > instead switch to simplified dates such as "1 day ago". Don't we use > PrettyDate elsewhere in the UX? We do, but a pretty date takes a lot of width.
blocking-basecamp: ? → -
Target Milestone: B2G C1 (to 19nov) → ---
Respectfully re-noming. * This is a notification system. It's near worthless without a time stamp. * This is not an addition. It's incomplete feature work. Etienne, let's format as follows: * Within past minute: Just now * Within past two minutes: 1 minute ago * Within past hour: 24m ago * Within past day: 2:45 PM * Within past week: Friday * Within past month: Feb 25 I've mocked that up here, and the sizing looks acceptable: https://www.dropbox.com/s/qnmzwbeamcge39q/Notifications_timeformats.jpg cc'ing Patryk to double check the visual consequences. In case of overflows, let's apply text-overflow:ellipsis to the first line of the Notification text. Re: localization, am cc'ing Stas. Stas, are other languages friendly to the sort of the truncation I'm using above? eg: "24m ago" = "24 minutes ago".
blocking-basecamp: - → ?
cc'ing Clee for product input on basecamp nom.
FWIW, I agree notifications without a timestamp are mostly useless, especially everything related to comms. IMHO, pretty dates will involve more work and risk + localization. I'd rather get this in with simple, raw date/times if necessary. Pretty dates are polishing; none at all is frustration.
Kaze, does the current l10n pretty date match Josh's suggestions? If it does let's go! If not it is indeed a risk.
Flags: needinfo?(clee)
Flags: needinfo?(clee) → needinfo?(kaze)
Pretty dates are supported by our l10n library already, but as Étienne mentioned it takes a bit of space (e.g. “3 hours ago”). If we want to use “compact” pretty dates (e.g. “3h ago”) it has to be modified a bit, and this should be a rather low-risk change. Using compact units such The other difference that I see with your proposal in comment #4 is that our pretty date lib doesn’t switch to absolute dates after a day: it says “4 days ago” instead of “Friday” or “Feb 25”. This part will have to be handled by the system app itself, our l10n_date lib already supports these human-readable date formats anyway. Overall, my opinion is that supporting compact, pretty dates for notifications in the same day would be worth it (not much more work + small risk).
Flags: needinfo?(kaze)
EDIT: (missing part) > using compact units such as 'h' and 'm' should be i18n-proof. I can work on this if it gets a bb+ label.
blocking-basecamp: ? → +
Priority: -- → P3
(In reply to Fabien Cazenave [:kaze] from comment #9) > EDIT: (missing part) > > using compact units such as 'h' and 'm' should be i18n-proof. I'm pretty sure you didn't mean it, but just to clarify: we should still put these short labels into shared/locales/date/date.en-US.properties, e.g. shortMinutesAgo[other] = {{m}}m ago
Depends on: 814355
follow-up: bug 814355 Staś: yes we should add these strings in the date.*.properties resources, but my point was that I /guess/ that this compact form (e.g. “18h ago” instead of “18 hours ago”) should exist in all supported languages — see comment #4.
blocking-basecamp: + → ?
Priority: P3 → --
blocking-basecamp: ? → +
Priority: -- → P3
Priority: P3 → P1
Target Milestone: --- → B2G C2 (20nov-10dec)
Etienne - please let us know if this is at risk for the C2 milestone so that we can try to find another assignee as necessary.
(In reply to Alex Keybl [:akeybl] from comment #12) > Etienne - please let us know if this is at risk for the C2 milestone so that > we can try to find another assignee as necessary. It really depends on the target date for bug 814355. Kaze?
Flags: needinfo?(kaze)
There’s a patch proposal for bug 814355, let me know if it suits your needs.
Flags: needinfo?(kaze)
Assignee: etienne → mbudzynski
Attached file patch
Attachment #688352 - Flags: review?(etienne)
(Easy) comments are on github :)
Attachment #688352 - Flags: review?(etienne) → review+
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: