Closed
Bug 656014
Opened 13 years ago
Closed 13 years ago
Add a way to prevent DisplayMessage (imap)= from marking a message as read automatically
Categories
(MailNews Core :: Networking: IMAP, defect)
MailNews Core
Networking: IMAP
Tracking
(Not tracked)
RESOLVED
FIXED
Thunderbird 5.0b1
People
(Reporter: protz, Assigned: protz)
Details
Attachments
(1 file)
996 bytes,
patch
|
Bienvenu
:
review+
|
Details | Diff | Splinter Review |
This is for Thunderbird Conversations. Rationale: - when we append messages to an existing conversation, we don't want these newly arrived messages to be marked as read ; if the user is doing something else, he might never notice these new messages when he moves on to another conversation ; - appending a message means expanding it, so that the users figures out which messages he should read in the conversation, - an expanded message is streamed through DisplayMessage for a number of reasons, - DisplayMessage, on IMAP, assuming autosync hasn't kicked in, decides to mark the message as read on the server side. This defeats the whole logic of Thunderbird Conversations. Because we're notified through the dbview that the selection has changed (a new message just arrived under the collapsed, selected thread) immediately, we often update the conversation before autosync has downloaded the messages. So that does happen. The attached patch adds a way to fix this, which Thunderbird Conversations intends on taking advantage of.
Attachment #531328 -
Flags: review?(dbienvenu)
Updated•13 years ago
|
Attachment #531328 -
Flags: review?(dbienvenu) → review+
Assignee | ||
Comment 1•13 years ago
|
||
http://hg.mozilla.org/comm-central/rev/7d96a5ff4809
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 3.3a4
You need to log in
before you can comment on or make changes to this bug.
Description
•