moving a floating event puts it in the default timezone

RESOLVED FIXED in Lightning 0.3

Status

Calendar
Internal Components
RESOLVED FIXED
12 years ago
11 years ago

People

(Reporter: dmose, Assigned: Joey Minta)

Tracking

({dataloss})

Trunk
Lightning 0.3
dataloss

Details

(Reporter)

Description

12 years ago
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.
(Reporter)

Updated

12 years ago
Blocks: 298366
(Reporter)

Updated

12 years ago
Assignee: shaver → nobody
(Reporter)

Comment 1

12 years ago
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.
(Assignee)

Updated

12 years ago
Blocks: 321164
(Reporter)

Comment 2

11 years ago
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: 298366
Target Milestone: --- → Lightning 0.2
(Assignee)

Comment 3

11 years ago
I'm pretty sure the patch on bug 323696 will solve this.
Assignee: nobody → jminta
(Assignee)

Comment 4

11 years ago
Fixed by bug 323696.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.