Open
Bug 208129
Opened 22 years ago
Updated 2 years ago
Status bar message doesn't get cleared ("Moving x of y messages to foldername")
Categories
(MailNews Core :: Networking, defect)
MailNews Core
Networking
Tracking
(Not tracked)
NEW
People
(Reporter: bugzilla2, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.5a) Gecko/20030601 Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.5a) Gecko/20030601 When dragging more than one message to another folder, the status message remains on the status bar indefinitely until something clears it. Reproducible: Always Steps to Reproduce: 1. Open MailNews 2. select more than one message and drag to another folder 3. observe status bar at bottom of screen Actual Results: The progress message "Moving 2 of 2 messages to (foldername)" stays displayed long after the process is completed Expected Results: The "moving..." message should get cleared, or changed to "MOVED 2 of 2 messages..." and then cleared in a few seconds. See related bug 208124 for another message that doesn't stay posted long enough.
This also happens when I mark email as Junk and they are automatically deleted. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a3) Gecko/20040719
Comment 2•20 years ago
|
||
This seems to happen with most messages in the status bar. Moving messages, retrieving messages, the bar never clears of the status message. Still trivial though
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•20 years ago
|
Assignee: sspitzer → mail
I have seen this bug too. It's still there on Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.8) Gecko/20051109 SeaMonkey/1.0b
Updated•19 years ago
|
Component: MailNews: Main Mail Window → MailNews: Networking
OS: Windows 98 → All
Product: Mozilla Application Suite → Core
Hardware: PC → All
Updated•16 years ago
|
Assignee: mail → nobody
QA Contact: esther → mailnews.networking
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
Updated•2 years ago
|
Severity: trivial → S4
You need to log in
before you can comment on or make changes to this bug.
Description
•