Open Bug 320456 Opened 14 years ago Updated Last year
When an event has neither DTEND nor DURATION, DTEND is added on serializing (upload/export)
(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.
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.
I don't think it's dataloss, the events are semantically identical with or without the DTEND property, no?
Stefan, I can imagine this one is fixed bug 390492, too?
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:188.8.131.52pre) Gecko/2008012808 Calendar/0.8pre Same behavior as described in Comment #0 still exists using storage provider. Seems to work now using ics provider.
(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.
You need to log in before you can comment on or make changes to this bug.