Closed Bug 23769 Opened 25 years ago Closed 25 years ago

No immediate Message pane refresh after Mark Message As Unread

Categories

(SeaMonkey :: MailNews: Message Display, defect, P3)

Other
Windows NT
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: fenella, Assigned: scottputterman)

Details

(Keywords: regression)

Win_nt 4.0 (2000-01-12-11 M13) Mac (2000-01-12-08 M13) Summary:[Regression]No immediate Message pane refresh after Mark Message As Unread Steps: 1. Launch Messager using the -mail option 2. From the Inbox, high-light a message and select Message|Mark|As Unread or Click on the diamond icon of a message Actual result: No response, the message does not change to Unread state However, two other situation exists: 1. if I exit/relaunch, the message is in Unread state and the message count shows correct count. 2. if I close the Inbox folder and re-open it, the message is changed to Unread state but the message count does not refresh to the correct count. Expected result: Message should immediately change to Unread when I do step 2. I should not have to exit/relaunch or Close/reopen folder. This problem only occurs in POP. Mac has the same problem. Unable to test Linux, Messenger crash when loading POP account (see bug 23750)
Assignee: phil → putterman
This works for me in yesterday's build, but maybe it's broken today? Reassigning to putterman
This is working for me on NT and POP. Is this still a problem, Fenella?
I will re-test this when today's builds are available.
QA Contact: lchiang → fenella
Keywords: regression
Summary: [Regression]No immediate Message pane refresh after Mark Message As Unread → No immediate Message pane refresh after Mark Message As Unread
Linux (2000-02-07-08 M14) commercial Win_nt 4.0 (2000-02-07-09 M14) mozilla Mac (2000-02-07-08 M14) mozilla This problem no longer exists. Mark it worksforme.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Mark it verified.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.