Closed
Bug 136943
Opened 23 years ago
Closed 23 years ago
Failures during drag and drop to mail folders
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: chris+bugzilla, Assigned: sspitzer)
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:0.9.9+)
Gecko/20020410
BuildID: 2002041003
When dragging mail messages from the thread pane to a folder in the folder pane,
I get the following error intermittently:
Error: [Exception... "Component returned failure code: 0x80004005
(NS_ERROR_FAILURE) [nsITransferable.getAnyTransferData]" nsresult: "0x80004005
(NS_ERROR_FAILURE)" location: "JS frame ::
chrome://messenger/content/messengerdnd.js :: DropOnFolderTree :: line 236"
data: no]
Source File: chrome://messenger/content/messengerdnd.js
Line: 236
When the drag and drop fails, it's usually after I've changed focus to the
thread pane. A second attempt (almost?) always succeeds. (the "almost" could be
explained by sloppy mousing and me missing the folder... I wasn't checking the
JS console constantly)
Reproducible: Sometimes
Steps to Reproduce:
1. Drag message to folder
Actual Results: message is not moved
Expected Results: message moved to folder
I did not see this bug in the previous nightly I used (20020404).
I have not encountered this problem using FizzillaCFM builds, including
2002041712 (RC1).
Chris, can you still reproduce this problem using a current build? Where do
these errors display? In the JS Console?
Reporter | ||
Comment 2•23 years ago
|
||
Greg: yes, I can reproduce this bug in RC1 and nightly 2002-04-25-03. The
errors show up in the JS console every time the drag fails. This bug looks like
a side effect of bug 30560, but that's just speculation. it was bad in the
04-10 build, got worse around the 04-14, 04-17 builds (I'm forgetting which of
those two was worse). The bug has been manifesting less frequently in RC1 and
the 04-25 build (which is the latest I've tried).
Reporter | ||
Comment 3•23 years ago
|
||
This bug is long gone. Thanks to whoever fixed it.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•