Closed Bug 304486 Opened 20 years ago Closed 19 years ago

moving a floating event puts it in the default timezone

Categories

(Calendar :: Internal Components, defect)

Product:
Calendar
Component:
Internal Components
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
Lightning 0.3

People

(Reporter: dmosedale, Assigned: jminta)

References

Details

(Keywords: dataloss)

It's possible this is lightning-specific, but I suspect not. Moving an event that's scheduled in floating time by dragging it causes it to be put in the default timezone.
Blocks: lightning-0.1
Assignee: shaver → nobody
Presumably something similar happens for Zulu events. For the moment, we'd like everything created in Lightning to be pinned to the default timezone. However, any events in a file that have some other modality (floating, Zulu, pinned to another timezone) should preserve that modality when modified either by dialog or drag-n-drop.
Blocks: 321164
0.1 is now targetted at no dataloss on self-generated data. Since we shouldn't be generating any floating events at the moment...
No longer blocks: lightning-0.1
Target Milestone: --- → Lightning 0.2
I'm pretty sure the patch on bug 323696 will solve this.
Assignee: nobody → jminta
Fixed by bug 323696.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.