Open
Bug 481284
Opened 15 years ago
Updated 2 years ago
Top-level account folders are still indicating new messages if this new messages are moved to another account by custom filters
Categories
(MailNews Core :: Filters, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: ShareBird, Unassigned)
References
Details
Attachments
(1 file)
28.20 KB,
image/png
|
Details |
If you have a new message in a folder, the folder and the top-level folder indicates you have a new message adding a small star to the icon. If you have this scenario: you have an account as top-level account. You have a filter which moves messages that fit the filter to another folder inside, e.g., Local Folders. This is what happens: a. Thunderbird receives a new message from the account you have the separated top-level account. The top-level account thinks "I have a new mail on my Inbox", so it becomes the small star. b. Your filter moves this new message to a folder inside the "Local Folders" top-level folder. The folder thinks "I have a new mail", so it has now the small star. But the two top-level folders (Local Folders and the top-level account folder) don't update the "has new message" status. It seems Bug 392637 is somehow related... I'm attaching an image which shows the issue.
Reporter | ||
Comment 1•15 years ago
|
||
Comment 2•15 years ago
|
||
Confirmed also here on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3pre) Gecko/20090815 Lightning/1.0pre Shredder/3.0b4pre ID:20090815035456
Updated•15 years ago
|
Component: Folder and Message Lists → Filters
Product: Thunderbird → MailNews Core
QA Contact: folders-message-lists → filters
Summary: Top-level account folders are still indicating new messages if this new messages are moved to another folder by custom filters → Top-level account folders are still indicating new messages if this new messages are moved to another account by custom filters
Comment 4•9 years ago
|
||
Removing myslef on all the bugs I'm cced on. Please NI me if you need something on MailNews Core bugs from me.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•