Closed Bug 168304 Opened 22 years ago Closed 21 years ago

Dragging attachment from message to message seems to work, but doesn't (should we disable it?)

Categories

(MailNews Core :: Attachments, enhancement)

x86
Windows 2000
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: francis+mozilla, Assigned: mscott)

References

Details

I'm using Mozilla 1.1, running against an Exchange IMAP server. I dragged an attachment, a zipfile, from the attachment pane of a message view window to the attachment pane of a message composition window. It seemed to work, so I sent the message. The recipient said the zipfile was corrupt; I did a View Source on the message, and found that all the MIME headers looked correct, but the content of the attachment body part was a very short snippet of base64; when decoded, it said something like "This body part will be downloaded on demand". I know that bug #160862 says that dragging out of the attachment pane isn't ready yet; maybe the Right Thing for now is just to disable pane-to-pane dragging until it works. (I certainly wouldn't miss it; this was the first time I'd ever tried it. :-)
QA Contact: trix → yulian
QA Contact: yulian → stephend
Setting severity to enhancement, confirming.
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Dragging attachment from message to message seems to work, but doesn't → Dragging attachment from message to message seems to work, but doesn't (should we disable it?)
I just tested this and it worked for a .JPG image; I had a problem with dragging a .EML attachment, which I'll detail in a different bug. John Stracke, if you are satisfied the problem has been addressed, please mark this bug Resolved|WorksForMe.
*** Bug 129280 has been marked as a duplicate of this bug. ***
No response from reporter; => WFM
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.