Closed Bug 339474 Opened 20 years ago Closed 18 years ago

Folder pane does not scroll when attempting to drag folder above or below visible area

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
All
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 343729
seamonkey2.0a1

People

(Reporter: lgrosenthal, Unassigned)

Details

(Keywords: regression)

User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.9a1) Gecko/20060525 MultiZilla/1.8.2.0i SeaMonkey/1.5a Build Identifier: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.9a1) Gecko/20060525 MultiZilla/1.8.2.0i SeaMonkey/1.5a When attempting to drag'n'drop a message folder from one area in the folder tree to another which is offscreen (above or below the visible portion of the folder list), the list does not scroll. Instead, an illegal mouse pointer is displayed. Reproducible: Always Steps to Reproduce: 1. Click and drag (RMB on OS/2; LMB on Win, etc.) a folder toward the top of the visible folder list (tree). Actual Results: Mouse pointer turns to "illegal" pointer. The folder cannot be dropped outside the visible list (obviously), and the list itself does not scroll up (or down) to follow the motion of the drag operation. Expected Results: Folder list (tree) should scroll up or down to the length of the list, allowing for the drop. As reported by Ruediger Lahl (see news://news.mozilla.org:119/e588ja.3dc.1@privat.lahls.de): 'Error console' reports this: |Error: uncaught exception: [Exception... "Component returned failure |code: 0x80004005 (NS_ERROR_FAILURE) [nsIDragService.invokeDragSession]" |nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: |chrome://messenger/content/messengerdnd.js :: BeginDragTree :: line |459" data: no]
With SM 1.5-0518 and with TB 3a1-0529, Win2K, I see the symptom of not being able to scroll the folder pane by dragging, but I don't see the JS error. Are current trunk Seamonkey builds using Toolkit? Perhaps this is toolkit bug 299971? See also bug 338401.
Severity: major → normal
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: unspecified → Trunk
not able to drop on top visible folder in folder pane is an additional symptom.
Severity: normal → major
I would also point out that this bug occurs for me when simply trying to drag a message from the message list into a folder that is beyond view in the folder list, or even a folder that is partially obscured. All of these show the illegal mouse pointer.
Toolkit bug 343729 is about this problem. I still don't know if SM trunk is using the toolkit, but if it is, this bug should depend on that one.
seamonkey trunk doesn't use toolkit yet, but it will. But bug 343729 regressed due to bug 326273, which was in XPCOM, so it's possible that it's not actually a toolkit bug at all.
By coincidence, I just filed Bug 370904 – In <messengerdnd.js>, "Error/Exception/NS_ERROR_FAILURE / nsIDragService.invokeDragSession / BeginDragTree :: line 459" which is separate from the current bug.
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.10pre) Gecko/20070219 SeaMonkey/1.0.8] (nightly) (W2Ksp4) [Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.2pre) Gecko/20070219 SeaMonkey/1.1.1] (nightly) (W2Ksp4) [Mozilla Thunderbird, version 1.5.0.10pre (20070219)] (nightly) (W2Ksp4) [Mozilla Thunderbird, version 2 beta 2 (20070219)] (nightly) (W2Ksp4) No bug. [Mozilla Thunderbird, version 3 alpha 1 (20070219)] (nightly) (W2Ksp4) [Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a3pre) Gecko/20070218 SeaMonkey/1.5a] (nightly) (W2Ksp4)
Depends on: 343729
Keywords: regression
(continuing previous comment :-|) Bug still there, in SM and TB Trunks.
now also in TB version 3 alpha 1 (20070319) (did not notice that in previous builds)
Sorry! What I wanted to say was: This also applies for dragging messages from message pane above and below folders in folder pane now, which I did not notice to happen before. Some (or one) builds ago, this was working.
(Thomas,) Dragging a message from the thread pane is how I discovered this bug; and it's what rudy wrote in comment 3. Can you confirm that it changed for you recently ? With a regression timeframe ?
Serge, I can confirm that. I do my "clean up" about once or twice a week, and I would have noticed, if this bug appeared before. So, it must have happend within the last two updates of 3a1. What I did in this timeframe was to uninstall antivirus software (Sophos, latest version) and install another one (NOD32). Nothing else in the system was changed. But I don't think, that there is any connection.
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9b4pre) Gecko/2008022702 SeaMonkey/2.0a1pre] (nightly) (W2Ksp4) R.Duplicate, per bug 343729 comment 23. *** Thomas, I'm not sure what to think about your comment(s). If you are still seeing something odd, file a separate bug.
Status: NEW → RESOLVED
Closed: 18 years ago
No longer depends on: 343729
Resolution: --- → DUPLICATE
Target Milestone: --- → seamonkey2.0alpha
I hope you are aware of the fact that your comment took almost one year? I hope this is not your average response time ;) Greetings
You need to log in before you can comment on or make changes to this bug.