Summary: | "Mark Thread Read" working as and when it feels like | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | BingMyBong <bingmybong> |
Component: | commands and actions | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bingmybong, montel |
Priority: | NOR | ||
Version: | 5.9.1 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Half the thread marked as read |
Description
BingMyBong
2018-09-19 12:01:05 UTC
More Info: The emails left as unread (ie. blue text) are identified as "read" (ie. black text) if you close kmail and reopen it so it just seems that its the cosmetic completion of the task that is the problem. I need to double check what happens if i "mark thread read" and then exit kmail (ie. no click further into the thread to make the unread count change) to see if the count and text colour is correct on reload of kmail (In reply to BingMyBong from comment #1) > More Info: The emails left as unread (ie. blue text) are identified as > "read" (ie. black text) if you close kmail and reopen it so it just seems > that its the cosmetic completion of the task that is the problem. > I need to double check what happens if i "mark thread read" and then exit > kmail (ie. no click further into the thread to make the unread count change) > to see if the count and text colour is correct on reload of kmail All is well on reload of kmail i.e. unread email count is correct and previous unread emails shown in blue text are now black text if I do the above indeed it seems to have some problem. I will investigate it Created attachment 117464 [details]
Half the thread marked as read
Just come across a strange result of "Mark Thread as read" that i have not seen before. I clicked on the root of the thread and pressed <Mark Thread as read> and parts of the thread were marked by being set to a black font colour. i've attached a screenshot of the 2 threads in question.
THis seems to be working fine now. Thanks !! |