Closed
Bug 17427
Opened 25 years ago
Closed 25 years ago
Mark as unread not working when the message has a replied status
Categories
(SeaMonkey :: MailNews: Message Display, defect, P3)
SeaMonkey
MailNews: Message Display
Tracking
(Not tracked)
VERIFIED
FIXED
M13
People
(Reporter: lchiang, Assigned: scottputterman)
References
Details
Mark as unread not working when the message has a replied status Win32 1999-10-27-09-m11 build Setup: IMAP although that doesn't really matter Steps: 1) Open Inbox 2) Select a message which has a "replied" status showing the thread pane 3) Click the green diamond or choose Message | Mark as Unread Actual results: Nothing happens. The message remains shown as read so that the green diamond does not appear or the message is not bolded Expected results: The message becomes bold and the green diamond appears to show that the message is unread Add'l Notes: No problem with marking a message as unread if the status of the message is read or no status.
Actually, I think that the message actually gets marked as unread. It's just not reflected back in the UI.
Assignee | ||
Comment 3•25 years ago
|
||
That would make sense. The bug is that both the diamond column and the status column are using the same RDF property. The property it is using talks "read", " ", "replied", etc. In reality, the diamond column only cares about "read" and " ". Therefore I need to split this into 2 separate properties so I can distinguish between the two.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M13
Assignee | ||
Comment 5•25 years ago
|
||
I have a fix for this. Will probably be checked in later this week.
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 6•25 years ago
|
||
I checked in the fix.
Linux Redhat 6.0 (2000-01-06-08 M13) Win_nt 4.0 (2000-01-06-09 M13) Mac (2000-01-05-15 M13) This problem has been fixed in these builds.
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•