When an event has neither DTEND nor DURATION, DTEND is added on serializing (upload/export)

NEW
Unassigned

Status

Calendar
Internal Components
12 years ago
10 years ago

People

(Reporter: Stefan Sitter, Unassigned)

Tracking

Details

(Reporter)

Description

12 years ago
(Bug filed after request in Bug 315719 Comment #6.)

After Bug 315719 is fixed, VEVENTs with neither DTEND nor DURATION will get
serialized to VEVENTs with DTEND. You might call this a datachange bug, because it is not really dataloss.
The bugspam monkeys have struck again. They are currently chewing on default assignees for Calendar. Be afraid for your sanity!
Assignee: base → nobody
Is this really dataloss, or is it more a side-effect of importing your calendar data into Sb/Ln? With importing, we expect some level of datamanipulation. With the provider, not so much.

Comment 3

11 years ago
I believe this is dataloss, because it happens in the providers and will happen when roundtripping any data in an ICS-based (eg ICS or CalDAV) calendar.
Keywords: dataloss

Comment 4

11 years ago
I don't think it's dataloss, the events are semantically identical with or without the DTEND property, no?

Comment 5

10 years ago
Stefan, I can imagine this one is fixed bug 390492, too?
(Reporter)

Comment 6

10 years ago
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12pre) Gecko/2008012808 Calendar/0.8pre

Same behavior as described in Comment #0 still exists using storage provider.
Seems to work now using ics provider.

Comment 7

10 years ago
(In reply to comment #6)
This fits my expectation. However since the ics part is fixed, I don't consider this being dataloss (comment #3) anymore.
Keywords: dataloss
You need to log in before you can comment on or make changes to this bug.