Exactly midnight-to-midnight events are displayed as time-based instead of all-day
This is a corner case that is different from #889, #1098 (closed), #172 (closed), #967, #968...
I believe it is only about the display/rendering of the events that are "midnight to midnight" across different dates within the same timezone (possibly broken encoding of all-day events by some other calendaring systems? Or is that actually spec-compliant?!)…
Mozilla's Firefox release dates only calendar (found on this wiki page, not yet on this page) is the test case for this. It contains events like these:
BEGIN:VEVENT
DTSTART:20240319T040000Z
DTEND:20240320T040000Z
DTSTAMP:20240223T190750Z
UID:22khvcbfrg5phethl8ljkmgcso@google.com
ATTENDEE;CUTYPE=RESOURCE;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;CN=mozilla.
com_2d37383433353432352d3939@resource.calendar.google.com;X-NUM-GUESTS=0:ma
ilto:mozilla.com_2d37383433353432352d3939@resource.calendar.google.com
CREATED:20230830T163006Z
LAST-MODIFIED:20230830T163006Z
LOCATION:Public - Firefox Merge/Release Schedule
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Firefox 124 released
TRANSP:OPAQUE
END:VEVENT
…we can see that it starts and ends at midnight UTC, on two different days, i.e. an exactly 24-hours event:
DTSTART:20240319T040000Z
DTEND:20240320T040000Z
The result is that GNOME Calendar 46 displays it as time-based:
Week view | Month view |
---|---|
However, Evolution displays it as an all-day event (which is what users would expect) instead: