Closed
Bug 50365
Opened 24 years ago
Closed 21 years ago
Stop button appears disabled in multi msg Copy/Move but actually isn't
Categories
(SeaMonkey :: MailNews: Message Display, defect, P3)
SeaMonkey
MailNews: Message Display
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: laurel, Assigned: scottputterman)
Details
Using aug25 commercial build
The Stop button appears disabled and unresponsive when moving or copying a large
multiple selection, particularly POP messages. Only on my very fastest machine
(mac G4) could I ever see the Stop button enable and appear responsive when
trying to stop a multi message copy or move.
In my testing for fix for bug 28129, I realize that although the Stop button
looks disabled, when I clicked the disabled button, I would eventually be able
to stop the POP copy/move. So it did work although it never appeared enabled.
1. Open a POP profile, go to mail window.
2. Select a folder with lots of messages... in my cases I was moving/copying
100-200 messages.
3. Edit|Select All or select 100 or so messages, then File/Move/Copy (by menu
or toolbar) them to another folder on that POP account or to a folder in Local
Folders.
4. Note the Stop button doesn't appear enabled. (Again, it appears enabled for
a flash nanosecond on my G4, but never on my 166mhz/NT or 400mhz/linux pcs.)
5. Click the (disabled) Stop button. Note it does wind up stopping the message
transfer, but doesn't look or "feel" enabled.
Updated•24 years ago
|
Summary: Stop button appears unresponsive in multi msg Copy/Move. → Stop button appears disabled in multi msg Copy/Move but actually isn't
Comment 1•22 years ago
|
||
this bug has not been touched since 2000-08-25, therefore this reminder.
Reporter could you please retest with a current mozilla build and let us know if
the problem is still present or the bug can be closed.
Comment 2•21 years ago
|
||
this is wfm with a current win2k trunk
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•