283388 - The red star over the account icons keeps appearing when it shoud disappear and vice-versa.

Status: RESOLVED INCOMPLETE

(Thunderbird :: Mail Window Front End, defect)

Description

[Dario Spadaccini]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803

The red star over an account icon should disappear when all new messages for
that account have been read, but this does not happen if the new messages have
been automatically put in Local folders by a rule.
The red star over an account icon should keeps appearing when at least a new
message for that account is still unread, but this does not happen if the new
unread messages have been automatically put in Local folders by a rule and the
Inbox (that does not contain any new message) is opened.
In other words:
1. The red star disappears opening the Inbox folder even if new messages have
not been read;
2. The red star does not disappear even if all the new messages have been read
in Local Folders.

Reproducible: Always

Steps to Reproduce:
1. Set a rule that puts new messages in a Local Folder
2. Get a new message trapped by the rule
3a. Open the new message stored in the bolded Local Folder
3b. Open the (not bolded) Inbox folder and the red star disappear
Actual Results:  
After steps 1-2-3a, the red star keeps appearing even if the new message for
that account have been read.
After steps 1-2-3b, the red star disappears even if there is still one unread
message for that account.

Expected Results:  
After steps 1-2-3a, the red star should automatically disappear.
After steps 1-2-3b, the red star should keep appearing.

Comment 1

[Mike Cowperthwaite]

This is the same issue as Seamonkey bug 116181.  I would dupe it except that 
it's filed against the front-end, which is separate from the TB front-end.
See also bug 272328, which is the same as Seamonkey bug 222068; all of these are 
probably the same bug once the code is tweaked.

Comment 2

[Dario Spadaccini]

IMHO, all the above mentioned bugs report the same bug as the 1-2-3a scenario.
On the other hand, the 1-2-3b scenario is (seems to be) a new bug.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Dario Spadaccini]

Just to let you know that both reported bugs are still happening on my Mozilla
Thunderbird version 1.5 Beta 1 (20050908).
I agree that the first reported bug is the same as the #116181 one.

Comment 5

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Reporter, does the issue still occur with the latest supported 2.0.0.x / Shredder trunk nightlies?

(1.5.0.x is now end-of-life and the latest supported Thunderbird version 2 is 2.0.0.16)

Comment 6

[Joshua Cranmer [:jcranmer]]

RESO INCO per lack of response to the last question. If you feel this change was made in error, please respond to this bug with your reasons why.