137907 - An "age" column in the list of messages, similar to the "date" column

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[Keith Lea]

personally I don't have a very good conception of absolute (as opposed to
relative) time, so I'd much rather see "Age: 3 days" than "Date: 4/14/02 6:00
PM" and "Age: 20 minutes" than "Date: 4/17/02 1:39 AM".

If I gave you a C function to convert a unixtime (seconds since 1/1/1970, unix
epoch, whatever you call it) to a char[], would this be more feasible?

thanks.

Comment 1

[Bruce Davidson]

*** Bug 138533 has been marked as a duplicate of this bug. ***

Comment 2

[Philip White]

Excellent idea; perhaps there could be an option to toggle between an absolute
date and an age.  Eudora Mail already offers age for e-mails, although I don't
know how flexible it is.
Confirming.

Comment 3

[Philip Andrew]

I agree that an "Age" field would be great; particularly, I sense, in a threaded
view, but probably I'd prefer that field to a date-stamp field (although I'd
probably display both).

However:  Is "Age" relative to "Date" of message, or "Date Received" of message?
 IMHO a rhetorical question, since I would assume that age relative to reception
of message is the most pertinent information a user would want to know.  For
most messages, "Date" and "Date Received" will be pretty close; and when they're
not, it's usually because the "Date" is incorrect (either deliberately, as with
some spam, or inadvertently, as with senders with incorrectly-set system clocks).

(ref: Bug 78025 -- talks about the addition of a "Date Received" field)

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420