10870 - [FEATURE] Drag and Drop of Messages

Status: VERIFIED FIXED

(SeaMonkey :: MailNews: Message Display, defect, P3)

Description

[scottputterman]

bug tracking feature in Summary.

Comment 1

[Phil Peterson]

Would like to have this for Seamonkey B1, but the latest word from the toolkit
group is that it won't be ready. Moving to M15

Comment 2

[Mike Pinkerton (not reading bugmail)]

no, the latest word from marketing was that we weren't doing d&d. it's not _our_
decision. I personally would like to fix all my d&d bugs. I hate how no one has a
straight story on all this.

Comment 3

[Phil Peterson]

Candice is working on this for M14

Comment 4

[chuang]

A new bug 25589 has filed for Folder drag & drop. Messages Drag & drop has 
checked in.
mailnews\base\resources\content\folderPane.xul (r1.43)
mailnews\base\resources\content\threadPane.xul (r1.46)
mailnews\base\resources\content\messenger.xul (r1.119)
mailnews\base\resources\content\messengerdnd.js (r1.2)

Comment 5

[(not reading, please use [e-mail] instead)]

wow, drag and drop of messages into folder really works? 

I can't test on linux, since D&D isn't working there.

does it file or copy? (or can I hold a key to make it do the other one?)

Comment 6

[chuang]

It's pretty much the same as 4.5.
Drag one or multiple messages(use ctrl, shift key) and drop within the same 
server will do a move, to different server will make a copy.  Ctrl + drag over 
to the same server doesn't make a copy yet, that's something I need to find out 
and maybe should file a bug on it.  

Comment 7

[(not reading, please use [e-mail] instead)]

note to qa:  d&d won't work on linux yet.  (#9642)

Comment 8

[lchiang]

fenella - can you verify?

Comment 9

[fenella]

Mac (2000-02-07-08 M14)
Win32(2000-02-07-09 M14)
Drag and drop works on Mac and Win_nt 4.0 in both POP and IMAP accounts.
It does not work on Linux yet. 
Leave this bug open until bg 9642 is fixed.

Comment 10

[fenella]

Bug 9642 has been fixed and bug 27295 has been opened to track drag and drop on
Linux. Mark this bug fixed.