Dragging events that span multiple days does not react/display properly

RESOLVED FIXED

Status

Calendar
Internal Components
RESOLVED FIXED
11 years ago
8 years ago

People

(Reporter: Joey Minta, Assigned: Joey Minta)

Tracking

({dataloss})

Trunk
dataloss

Details

Attachments

(1 attachment)

(Assignee)

Description

11 years ago
For events that span more than one day, there are multiple boxes associated with the single event.  They are all selected properly, but the drag-code doesn't know how to handle this case.  These type of events, when dragged, may behave in appropriately.  (They'll likely be shortened to only 1 day.)

Updated

11 years ago
Keywords: dataloss

Updated

11 years ago
Whiteboard: [cal relnote]
(Assignee)

Comment 1

11 years ago
Created attachment 213922 [details] [diff] [review]
restructure assignment of drag times

Medium risk.  Changes the way we assign times to events, at the end of a drag, working from the event's original start/end times, rather than from the column's date.  Fixing the modify-start and modify-end cases was pretty trivial and I would consider it low risk.  The move case was more difficult, because of the possibility of dragging across days, but not overly scary.
Assignee: base → jminta
Status: NEW → ASSIGNED
Attachment #213922 - Flags: first-review?(dmose)
(Assignee)

Updated

11 years ago
Blocks: 330188
Patch works as advertised against trunk on Mac OS X 10.4
(Assignee)

Updated

11 years ago
Attachment #213922 - Flags: first-review?(dmose) → first-review?(mvl)
Comment on attachment 213922 [details] [diff] [review]
restructure assignment of drag times

r=mvl
Attachment #213922 - Flags: first-review?(mvl) → first-review+
(Assignee)

Comment 4

11 years ago
Patch checked in.
Status: ASSIGNED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
Whiteboard: [cal relnote]

Comment 5

8 years ago
Filed a possible followup bug to build a correct shadow when events that spanning multiple days are dragged in week view: bug 533414.
You need to log in before you can comment on or make changes to this bug.