Closed Bug 1606391 Opened 4 years ago Closed 4 years ago

Display of multi-day events starting 29 Dec ending part way through 01 Jan 2020 but appears to end at 23:59 (00:00) 31 Dec (2020)

Categories

(Calendar :: Calendar Frontend, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1572964

People

(Reporter: graham, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0

Steps to reproduce:

Using Thunderbird 68.2.2 (64-bit)....
Create multi-day event in Thunderbird calendar starting anytime during 29 Dec (2019) or any prior date) and ending part way through date on or after 01 Jan (2020).

Actual results:

Appearance of created event in Calendar starts at correct time on 29 Dec but appears to end at 23:59 (00:00) 31 Dec (2020). The event does not continue into the next (or subsequent) day(s).

Expected results:

Event should appear to start at specified start time and date and end at specified end time and date.

Oddly, it displays correctly if the start time/date is anytime during 30 Dec (2019).

FWIW, if I do the same in my CalDAV server calendar (multi-day event starting 29 Dec and finishing > 00:01 01/01/(2020), it displays correctly on the server, but Thunderbird Calendar f**ks it up.

Y'know, once upon a time I described Thunderbird 60 as the biggest c**k up rewrite mess the developers had made. Now, I'm thinking 68 might be the new record.

Component: Untriaged → Calendar Views
Product: Thunderbird → Calendar
Version: 68 → unspecified
Summary: Display of multi-day events starting 29 Dec → Display of multi-day events starting 29 Dec ending part way through 01 Jan 2020 but appears to end at 23:59 (00:00) 31 Dec (2020)

Could be duplicate of bug 1572964. Do you still see the problem using the Thunderbird 68.3.1 + Lightning 68.3.1?

Flags: needinfo?(graham)

(In reply to Stefan Sitter [:ssitter] from comment #1)

Could be duplicate of bug 1572964. Do you still see the problem using the Thunderbird 68.3.1 + Lightning 68.3.1?

No. Thunderbird 68.3.1 fixes the problem.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Flags: needinfo?(graham)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.