Closed
Bug 16839
Opened 25 years ago
Closed 25 years ago
Synching of flag states isn't committed or reflected in UI
Categories
(MailNews Core :: Backend, defect, P3)
MailNews Core
Backend
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: laurel, Assigned: Bienvenu)
Details
Overview: Synchronizing of flag states isn't being committed to the database,
or reflected in the UI. I discovered this while testing IMAP Mark Read filter
action (ref bug #10295).
1. You have an imap account which is already set up in 5.0. You do not have
that account currently open in 5.0
2. Launch that imap account using Communicator 4.6, Open Inbox, provide
correct password, mark some existing/read messages Unread.
3. Exit Communicator 4.x
4. Launch mail in 5.0 and check the read status of those messages which you
marked unread in 4.x.
Actual results: They still show as read in seamonkey/5.0
Expected results: They should display unread status.
Found using 1999-10-19-08m11 commercial builds on NT 4.0 and Linux 6.0
Mark an existing message unread with 4.5, shutdown 4.5, and
start up 5.0. If the message is still shown as read in 5.0, then we're not
synchronizing correctly.
Assignee | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 1•25 years ago
|
||
fixed in nsImapMailFolder.* to add a SyncFlags method.
OK using 1999-10-26-08m11 commercial linux 6.0
OK using 1999-10-26-08m11 commercial NT 4.0
OK using 1999-10-26-08m11 commercial mac os 8.5.1.
Updated•20 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•