Closed
Bug 462850
Opened 16 years ago
Closed 16 years ago
Drag and Drop calendar entry locks up program / OS
Categories
(Calendar :: Calendar Frontend, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 348009
People
(Reporter: scott.benninghoff, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.3) Gecko/2008100613 Gentoo Firefox/3.0.3 Build Identifier: version 2.0.0.17 (20081006) Drag a calendar (appointment) to another day. Let go of left button while moving and the appointment will not drop and after that no keys will allow drop of the appointment (either from the keyboard or mouse). Had to kill application from another terminal. Can't even switch to another application w/in O.S. Once Thunderbird is killed, OS begins to respond and keyboard/mouse activity begin to operate normally. Reproducible: Always Steps to Reproduce: 1. Select appointment on any given day (month calendar view) 2. Drag that appointment to another day, while moving the mouse, release left button 3. Drag Icon will not change and the movement of the mouse continues to be the appointment. Actual Results: Program is stuck, have to kill to get back to O.S. Expected Results: at some point timeout of drag / drop operation and leave original appointment intact. Failed drag drop operation.
Reporter | ||
Comment 1•16 years ago
|
||
I should add. When you have moved the appointment to the Target Date (box), an appointment block becomes highlighted. i.e. Monday is the selected date, quickly moving to Tuesday and letting go of the mouse (Monday is still highlighted) is when this behavior is exhibited. Dragging to a date where that date is hightighted and dropping works fine.
Comment 2•16 years ago
|
||
What Lightning version do you use? This sounds like Bug 348009 that ought to be fixed in Lightning 0.9.
Reporter | ||
Updated•16 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 4•16 years ago
|
||
Downloaded .9 and it works.
Updated•16 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•