263601 - Can't drag&drop with other apps while Mozilla moves messages

Status: NEW

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Ben Bucksch (:BenB)]

Reproduction:
1. Open a folder with 6000 msgs. Select all, drag&drop them into another folder
(with 130000 msgs in my case) to move them.
2. While the operation is in progress, drag a fielsystem folder from Konqueror
into the XMMS main window.

Actual result:
Nothing.

Expected result:
The file folder from Konqueror is being loaded as new playlist in XMMS. This is
what happens when move msg operation is in progress in Mozilla.

In both cases, while the cursor is over XMMS, a (/) (operation not allowed) sign
flashes. Nevertheless, the operation works in one case.

System:
- Mozilla 1.7.something derivate
- SuSE9.0
- file folder was NFS share containing lots of MP3s

Comment 1

[Ben Bucksch (:BenB)]

> This is what happens when move msg operation is in progress in Mozilla.

... when *no* move msg operation is in progress...

Comment 2

[Serge Gautherie (:sgautherie)]

MozillaAS v1.7.x is not supported anymore.

Can you reproduce with SeaMonkey v1.1.9 ?

Comment 3

[Ben Bucksch (:BenB)]

How about you trying yourself? There's a clear reproduction description.

Comment 4

[Serge Gautherie (:sgautherie)]

Because I have no Linux, no NFS share, no folder with 6.000 or 130.000 messages, ...
I don't understand how you expect someone else to test "your" (4 year old) computer/network/setup ?
We would like your help !

Comment 5

[Ben Bucksch (:BenB)]

> Because I have no Linux

Then don't comment, please. It's just as hard for me to reproduce 4 years old bugs as it's for you.

Comment 6

[Serge Gautherie (:sgautherie)]

(In reply to comment #5)
> Then don't comment, please.

Nobody looked into this bug (and many others) for the past 3.5 years.
Not commenting does not help anything;
whereas "re-triaging" will help, other (current) bugs if not this (old) one.

> It's just as hard for me to reproduce 4 years old bugs as it's for you.

(Probably a little bit less, but) I'm sure it is.
The point is that if even you (= the reporter) can't reproduce it (nowadays),
then this bug should be resolved worksforme/incomplete/invalid.

Comment 7

[Ben Bucksch (:BenB)]

> this bug should be resolved worksforme/incomplete/invalid.

No! That's *exactly* why I hate these questions. I took considerable work to file these bugs. If nobody cares so far, that's not my fault.
If nobody proves the bug is gone, we have to assume it still exists.

Please do not comment anymore unless you can *add* information to bugs. Thank you. End of subject.