Closed Bug 298609 Opened 20 years ago Closed 19 years ago

Crash when dragging files from open email to another email window

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: chris, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: 

Thunderbird crashes when files from an open email are dragged onto the window of
another composed email.  You must drag them onto the app bar since the composed
email is usually hidden or minimized.  Mistakenly dragging over another
application or window and back either crashes Thunderbird or causes the drag
operation to stop.  This makes dragging files to other applications or emails
very difficult.

Reproducible: Always

Steps to Reproduce:
Drag the files to the app bar and over the new email.
** Note that the save dialog opens at this point but ignore it.  I'm not sure
why it opens on a drag operation
Now drag over another window button and back and forth to composed email.
thunderbird will crash with a NPE either right away or within a few seconds.
Actual Results:  
thunderbird crashes with an NPE or drag operation is cancelled unexpectedly.

Expected Results:  
I should be able to drag the files to another email and onto the Attach Files
area to be send.

thunderbird 1.0.2 with Windows 2000 SP4
Does the Talkback agent open when you crash? If yes, can you send such a
talkback report and open talkback.exe in your components folder (in your
Thunderbird program folder) and give use the Talkback ID of this crash?
No talk back does not open.  One crash simply closed the window with no dialog
at all.  Another crash showed a message box:

thunderbird.exe
code at 0x00000000 executed instruction 0x00000000
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.