Closed
Bug 397470
Opened 17 years ago
Closed 17 years ago
Agenda & Miniday: Third header with date range is too long
Categories
(Calendar :: Lightning Only, defect)
Calendar
Lightning Only
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: mschroeder, Unassigned)
References
Details
If miniday != today, third section of Agenda doesn't include only events for the day after tomorrow in relation to the selected miniday as suggested by the section header.
Flags: blocking-calendar0.7?
Comment 1•17 years ago
|
||
[I hope I understand your description correclty, but]
IMO not a bug since the third section header states the date range of items it is hosting. Worth a UI review/comment from Christian, of course.
Severity: major → normal
Flags: blocking-calendar0.7? → blocking-calendar0.7-
Comment 2•17 years ago
|
||
I agree that its non-blocking, but I had to enlarge the today-pane to double size to see that it states a date range. So this needs an UI improvement.
Reporter | ||
Updated•17 years ago
|
Severity: normal → minor
Summary: Agenda & Miniday: Third section doesn't include only events for the day after tomorrow → Agenda & Miniday: Third header with date range is too long
Target Milestone: 0.7 → ---
Comment 3•17 years ago
|
||
In my implementation of bug 389854, that I will provide in the coming days I skip the 'tomorrow' and 'soon' section when the today-pane is not in "today-mode". If the today-pane shows the day of "today" than the user will probably also want to have information about the following days, but if he selects an arbitrary date in the past or future I don't think this is very useful.
Reporter | ||
Comment 4•17 years ago
|
||
(In reply to comment #3)
This sounds like the bug will become invalid when the "new agenda" lands. :)
Depends on: 389854
Flags: blocking-calendar0.7-
Reporter | ||
Comment 5•17 years ago
|
||
This bug is INVALID after design changes from bug 389854.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•