Closed
Bug 24787
Opened 25 years ago
Closed 23 years ago
Displaying an IMAP message more than once in one session doesn't mark the message read
Categories
(MailNews Core :: Backend, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla0.9
People
(Reporter: scottputterman, Assigned: Bienvenu)
References
Details
(Whiteboard: [nsbeta1+])
Attachments
(1 file)
3.60 KB,
patch
|
Details | Diff | Splinter Review |
This happens on IMAP, not POP. Open an IMAP folder. Display a message. Display a second message. Click on the green diamond of the first message you display to mark it unread. Display the first message again. result: The first message isn't marked read. expected: The first message gets read. I'm taking a guess here, but are we reading from the Memory Cache the second time we display the message? And if we are, does that hit the code that marks the message read?
Comment 1•25 years ago
|
||
we are indeed hitting the memory cache the 2nd time you read the message and indeed you are correct, I don't run through any of the code that would mark a message read in this scenario. =P
Assignee | ||
Comment 2•25 years ago
|
||
4.5 handled this case by noticing when we're pulling an unread message out of the memory cache, and marking it read when we're finished.
Updated•24 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → M18
Comment 7•24 years ago
|
||
I don't think this is an important bug to fix for beta3 or RTM. I'd probably rank thinks like SSL on the Mac higher than this. I'd like to mark this future.
Assignee | ||
Comment 8•24 years ago
|
||
this bug is driving me crazy. I'll fix it.
Assignee: mscott → bienvenu
Status: ASSIGNED → NEW
Assignee | ||
Comment 10•24 years ago
|
||
it's also been filed as a bug many times, which means to me that people run into it.
Status: NEW → ASSIGNED
Assignee | ||
Comment 11•24 years ago
|
||
I have a fix for this - it was a bit more code than I would have hoped, trying to get from here to there (consing up nsISupportsArrays, etc), but it works fine.
Whiteboard: [nsbeta3+] → [nsbeta3+]Fix in hand
Assignee | ||
Comment 12•24 years ago
|
||
fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Comment 13•24 years ago
|
||
OK using: 2000-08-17-13 commercial build linux rh6.0 2000-08-17-08 commercial build mac OS 9.0 and NT 4.0
Status: RESOLVED → VERIFIED
Assignee | ||
Comment 14•23 years ago
|
||
new memory cache landing broke this, so I'm re-opening.
Reporter | ||
Comment 15•23 years ago
|
||
It would be great if this could get fixed for 0.9 (I'm very good at getting hit by this)
Priority: P3 → P1
Whiteboard: [nsbeta1+]
Target Milestone: M18 → mozilla0.9
Assignee | ||
Comment 16•23 years ago
|
||
OK, I think the reason this is broken is that now we get notified asynchronously that a mem cache entry exists (this still seems bogus to me, but that's a different story). The way it use to work was that if we're reading from the mem cache, in FetchMessage, we set a flag on the url that says we're loading it from the cache, and nsImapService::DisplayMessage would check that flag and mark the message read. But now the code that sets the flag on the url happens after we check it in nsImapService::DisplayMessage. So, we're going to need to find a place to move that code that checks the flag and marks the message read.
Assignee | ||
Comment 17•23 years ago
|
||
Comment 18•23 years ago
|
||
r=naving
Comment 19•23 years ago
|
||
sr=sspitzer news has the same problem. I'll log a bug on that.
Assignee | ||
Comment 20•23 years ago
|
||
fix checked in.
Status: REOPENED → RESOLVED
Closed: 24 years ago → 23 years ago
Resolution: --- → FIXED
Comment 21•23 years ago
|
||
OK using apr18 commercial trunk build: win98, linux rh6.2
Comment 23•23 years ago
|
||
*** Bug 78321 has been marked as a duplicate of this bug. ***
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•