140090 - Green mail arrow (biff) persists in compose window's component bar

Status: RESOLVED DUPLICATE of bug 177887

(SeaMonkey :: MailNews: Message Display, defect)

Description

[JWBohrer]

From Bugzilla Helper:
User-Agent: (Spoofed as:) Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4)
Gecko/20011128 Netscape6/6.2.1
BuildID:    2002041711

Sometimes the green new mail arrow on the envelope icon in the lower left
appears when composing a new message. The tray icon does not appear and no new
messages are present. It doesn't appear on any other windows open, either, just
the current compose window. Right now it is doing it everytime I open the
compose window. I have mail/news open and maximized, address book open and
maximized and this single browser window open and maximized with no tabs open.

Reproducible: Sometimes
Steps to Reproduce:
1. Click Compose
2.
3.

Actual Results:  Compose window comes up, but with a green arrow on the envelope
icon

Expected Results:  Compose window should have come up with no green arrow

modern theme, Mozilla RC1 spoofed as NS 6.2.1, windows 98SE

Comment 1

[JWBohrer]

Persists in RC2 download, this is strange. Am I the only one who is seeing this?
This is a strange bug, in that when it happens it happens regularly, with every
new compose window, until a restart. But so far I haven't been able to figure
out the trigger.

This time I also have Mail/News opened, single browser window open but three
tabs, so I guess the nubmer of tabs opened does not matter. 

Clicking "get all new messages" doesn't get rid of the arrow.

Neither does manually checking all accounts or sending myself a new message.  

This happens when using both "reply" and "compose"

Comment 2

[Mike Cowperthwaite]

JWBohrer, are you still seeing this in current (Netscape 7, Moz 1.3 or 1.4) 
builds?

Comment 3

[JWBohrer]

Still here, I also see it on my XP Pro laptop. It seems to happen after new mail
arrives and is viewed, then can be triggered by either a reply or a compose.
Because I'm the only one reporting this, it is probably a product of a
particular combination of Netscape/POP accounts. The common denominator on my
two systems is one Netscape Account and one POP account. On my '98 system I also
have a newsgroup account and another POP account. I'll make particular note of
what happens the next time I see it and report back. I don't have any Mozilla
installed anymore, just the latest NS7 product so I can't comment on the latest
builds.

Comment 4

[Roscoe Primrose]

I'm seeing this on OSX with 2003061108.

Comment 5

[Mike Cowperthwaite]

I am confirming this because I got into this state with
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030527

However, I have not been able to figure out how I did it.  I was writing a 
message when I noticed that new mail had arrived; I'm not sure if the new mail 
was there before I hit the Compose button.  Before sending my message, I jumped 
over to the main window and read all the new mail; as soon as I clicked on the 
first message, the biff arrow disappeared from the main window's component bar, 
and the icon from the task bar (which I believe is expected); but when I 
returned to my compose window, the component bar still showed the green arrow.  
Opening additional compose windows had the same indicator.  Sending my message 
and then opening additional compose windows -- again, still showing the arrow.

There has to be some sort of timing thing between the arrival of the mail and 
the process of composing a message.

Comment 6

[Luke Reeves]

This happened to me also using "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.6b) Gecko/20031208".  I suspect it's the junk mail filter tripping it.  See
also bug 228131.

Comment 7

[JWBohrer]

No--this predates the junk mail filter by a long time. But I would say that junk
mail tripping the new mail notification should be a bug, and I believe it is
already reported. 

Comment 8

[Roscoe Primrose]

Seeing the same behavior on OSX w/2003120905, OS should probably be changed to
all...

Comment 9

[Aleksey Nogin]

Bug 177887 has a patch.

*** This bug has been marked as a duplicate of 177887 ***