193974 - [mailviews] Last 5 days should work on days and not a strict 24 hour clock

Status: NEW

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Ninoschka Baca]

Trunk build 2003-02-14: WinXP, Mac 10.1.3

Overview: If I select the MailView for the "Last 5 days" I expect to see
messages  based on the entire day and not a strict 24 hour clock. For instance
if it is Friday and I select to view messages for the "Last 5 days" I expect to
see all the messages from Monday-Friday. Instead, it works on a 24 hour clock so
if it is Friday at 1pm I won't see messages from Monday AM. The later it gets,
then fewer messages will appear from Monday.

Expected Results: I would like "all" the messages starting from Monday at
midnight to Friday at the present time, to display.

Comment 1

[Ninoschka Baca]

Marking nsbeta1. This confused me and I thought I had lost some messages. Most
people, when reading email, don't think in terms of a 24 hour clock. They look
for messages from a specific day.

Comment 2

[Stewart Gordon]

I guess whoever coded it up likes the idea of a day being 24 hours.  But surely what 
you've described would be last _4_ days?

They probably should be two separate view options - "Last X blocks of 24 hours" and 
"Last X calendar days".

Stewart.

Comment 3

[Stewart Gordon]

I guess whoever coded it up likes the idea of a day being 24 hours.  But surely what 
you've described would be last _4_ days?

They probably should be two separate view options - "Last X blocks of 24 hours" and 
"Last X calendar days".

Stewart.

Comment 4

[Samir Gehani]

Mail triage team: nsbeta1-

Comment 5

[(not reading, please use [e-mail] instead)]

ninoschka, how did 4.x behave?  (adding 4xp)

sounds like a bug in how we implemented age in days.

Comment 6

[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 7

[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

Comment 8

[Eyal Rozenberg]

Seems a perfectly valid idea to me, although not that important.