Open
Bug 1120152
Opened 11 years ago
Updated 3 years ago
Dragging a mail or attachment to/from Thunderbird indicates move, not copy
Categories
(Thunderbird :: OS Integration, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: roland.illig, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36
Steps to reproduce:
I started Thunderbird. In the list of mails, I started dragging one mail to the Windows desktop.
Actual results:
The dragging mouse cursor shows just a rectangle. This means to _move_ the mail to the desktop, so it will be deleted in Thunderbird. To be confident that the mail doesn’t get deleted in Thunderbird I have to press Ctrl during dragging, which shows the [+] overlay on the mouse cursor.
Expected results:
The dragging mouse cursor should have the [+] overlay to indicate copying.
| Reporter | ||
Comment 1•11 years ago
|
||
The same happens when I drag something into a new mail being composed in Thunderbird. This should not be "Move" like in the image, but "Copy".
| Reporter | ||
Updated•11 years ago
|
Summary: Dragging a mail or attachment outside of Thunderbird indicates move, not copy → Dragging a mail or attachment to/from Thunderbird indicates move, not copy
Comment 2•11 years ago
|
||
Thanks Roland, indeed, mouse pointers should always indicate the actual action correctly, so it should have a [+] icon when copying (vs. moving).
Richard, can you look into this?
Flags: needinfo?(richard.marti)
Comment 3•11 years ago
|
||
Yes, confirmed, drag and drop from or to TB should always indicate the copy function.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(richard.marti)
| Reporter | ||
Comment 4•11 years ago
|
||
When I drag a large attachment from Thunderbird to the desktop, a Windows dialog opens that also says "Moving files". I expect that this will be fixed automatically when the icon changes, but it should be tested as well.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•