109950 - message header display is hosed: Shows * in headers

Status: RESOLVED WORKSFORME

(SeaMonkey :: MailNews: Message Display, defect, P1)

Description

[K Chayka]

win32 build 2001111303, win98se, appears to be a problem only in Classic

In the 3-pane view, the message header bar gets completely lost after a while -
the header that displays is for some previously read message, or it just
contains garbage.  Happens with both mail and news and removing msf files does
not help. The js console shows repeated instances of

Error: emailAddressNode.setTextAttribute is not a function
Source File: chrome://messenger/content/msgHdrViewOverlay.js
Line: 619

And an occassional
Error: document.getAnonymousElementByAttribute(this, "anonid", "headerValue")
has no properties
Source File:
chrome://messenger/content/mailWidgets.xml#mail-headerfield.headerValue (setter)
Line: 0

Shutting down and restarting only corrects it sometimes, and then only
temporarily.  Bug 109912 that I filed earlier today may stem from the same cause.

Comment 1

[Chase Tingley]

confirming; i see this on 2001111109 linux using the classic theme.

this is indeed ugly; much of my work mail claims to have "Newsgroups:
netscape.public.mozilla.performance", which I certainly hope is not true.

Comment 2

[K Chayka]

Attachment: screen shot of Modern

I guess it's not just Classic after all.  When this happened, the js console
showed
Error: emailAddressNode has no properties
Source File: chrome://messenger/content/msgHdrViewOverlay.js
Line: 618

It happened after switching to a different newsgroup.  After this, the next
message displayed seemed OK except for odd line wrapping in the subject, and
the message after that had the header for the previous message.

Then switched from news to a mail folder, and read a message.  The header shown
is from the last news post that was read.  This was accompanied by
Error: emailAddressNode.setTextAttribute is not a function
Source File: chrome://messenger/content/msgHdrViewOverlay.js
Line: 619

Bad mozilla, bad. :-(

Comment 3

[(not reading, please use [e-mail] instead)]

msg display -> mscott.  he may have fixed this a few days ago.

Comment 4

[Scott MacGregor]

I saw this briefly in a build earlier this week but made some changes on Tuesday
which I think fixed this. Please try again on a build from today and let me know
if you still see it.

Comment 5

[laurel]

I'm not able to reproduce the condition using nov15 commercial trunk build win98
in either classic or modern themes.
Marking verified and reporter can reopen if necessary.

Comment 6

[laurel]

I just saw this using linux rh6.2 with nov15 commercial trunk build. I'd just
sent a mail message, went to the Sent folder to take a look at it and found its
headers 
fields were all displaying an asterisk (just like the attachment screenshot from
11/13 shows). Not sure I can reproduce, but I saw it.

Comment 7

[laurel]

OK, I see the asterisk header display on each and every message sent on my linux
machine.  If I select another message and come back, the asterisks are properly
replaced with content. 

Comment 8

[laurel]

Added info: I see this when using either All or Normal headers on linux, am now
able to reproduce on win98 only when using All headers display. Don't know that
that makes sense, but it's what I'm seeing.  Both machines are in Modern theme.

Comment 9

[laurel]

Able to reproduce with the compose/send/look at Sent folder scenario on Mac OS X.

Comment 10

[laurel]

*** Bug 110440 has been marked as a duplicate of this bug. ***

Comment 11

[laurel]

*** Bug 111149 has been marked as a duplicate of this bug. ***

Comment 12

[laurel]

*** Bug 107253 has been marked as a duplicate of this bug. ***

Comment 13

[Francisco León]

From my recently duped bug (which was older than this):
"I just sent mail to 3 different persons in one mail. One was TO: , the other 2
were CC. I included a "Reply to:" header because i needed."

This is what i did to reproduce this

Comment 14

[R.K.Aa.]

*** Bug 110070 has been marked as a duplicate of this bug. ***

Comment 15

[scottputterman]

I just saw this on the 12/14 build.  I selected a message that had just come in.
 The From said "*" and the CC said "*".  The To was blank.  I saw this on
lchiang's machine yesterday as well.  I'm not sure which build she was using. 
As soon as I switched messages, the headers displayed correctly and going back
to the incorrect message made that message display correctly.  

Comment 16

[scottputterman]

Since the original reporter's screenshot shows the "*" in the headers I'm adding
this to the summary.

Comment 17

[scottputterman]

*** Bug 115344 has been marked as a duplicate of this bug. ***

Comment 18

[scottputterman]

I don't know if this is related.  I just got another message where only 3
headers were showing in the To field with no twisty.  I selected another message
and came back and then there was a twisty.  I opened it up and the To field now
had 6 headers.

Comment 19

[scottputterman]

I guess it's sort of ironic that the next time I saw the "*" problem was on the
bug email for the last comment I added for this bug. I see the same js error as
the very first comment in this bug, so everything the original reporter wrote
appears to hold true on 12/14.  I am using Modern, not Classic, however.

Comment 20

[lchiang]

More symptoms/clue to help narrow down further:

Win2k, 2001-12-17-06-trunk build

I see this problem when I switch to another folder and select a message which
was just downloaded into that folder (via a filter).

Using IMAP, modern skin, show normal headers.

Comment 21

[scottputterman]

I was seeing this a bunch in mid December.  I haven't seen it in a while.  Are
people still seeing this?

Comment 22

[K Chayka]

I saw it once a day or two ago, win32 build 2002011003
I hadn't seen it in a few weeks, and thought it might have been fixed, but I
guess not.

Comment 23

[lchiang]

Have not observed this for a few weeks now.

Comment 24

[scottputterman]

I just saw this today.

Comment 25

[Suresh]

I saw this again today using 1/16 windows comm build.

Comment 26

[lchiang]

Observed in the 2-12-2002 Win2K build after an absence of seeing this.  Will try 
to see if I can get it to reproduce.

Comment 27

[Suresh]

fyi: yeah, I saw this too very recently. The headers displayed "*" in From and
To fields and blank in rest of the fields. 

Comment 28

[scottputterman]

I haven't seen this in a while.

Comment 29

[Håkan Waara]

Does anyone have a reproducible testcase for this?

Comment 30

[Francisco León]

read comment 13, that is my testcase (havent retested but should work)

Comment 31

[scottputterman]

reassigning to ssu.

Comment 32

[Sean Su]

I have seen this in earlier builds, but not in the recent ones (less than 2
weeks old? I'm guessing).  I can't reproduce this.  I also tried what was said
in comment 13, still no luck.

Can any reproduce this in a recent build?  if not, I'll close this bug as
worksforme.

Comment 33

[laurel]

I've not seen it recently, can't reproduce.

Comment 34

[Sean Su]

closing as worksforme.  please reopen if this comes back.

Comment 35

[laurel]

marking verified worksforme

Comment 36

[scottputterman]

reopening.  I just saw this on the 3/15 build which is after this bug was marked
WFM.  I'm going to remove the nsbeta1+ for now because I think once in the last
few months isn't worthy of an nsbeta1+ given that you can click on another
message and reload it.  But if other people start seeing this again, please
comment in this bug.  The frequency might help it get plussed again.

Comment 37

[scottputterman]

Is anyone else seeing this?  I've seen this about 10 times since downloading the
3/15 build (I'd try a later build but they don't look safe to use, yet).

Comment 38

[Sean Su]

I haven't seen this lately yet.  I'm currently running the 18th build under win2k.

Comment 39

[[e-mail]]

I see this randomly. Is the XBL binding not getting attached in a timely
fashion? I've got a similar problem with the tabbed browser not creating tabs
properly :-(

Comment 40

[K Chayka]

win32 trunk build 2002063004, win98se

Saw it again, after several months of not seeing it at all.  Sequence of events
(to the best of my recollection):

1. Started mail-news
2. Clicked on news.mozilla.org folder twisty, folder expanded and unread message
counts were updated in the folder pane
3. Read selected unread messages in a few groups (not using any keyboard
shortcuts), the last one before the empty header showed up was n.p.m.mail-news.
4. Mark All Read (CTRL-SHIFT-C) for n.p.m.mail-news.  I think focus was on the
threadpane at the time.
5. Used tab key to move back to the folderpane.
6. Arrowed down folderpane to n.p.m.ui, Threads With Unread displayed in the
threadpane, the first thread was automatically expanded (3 messages in that
thread, 1 unread)
7. Used tab key to move from folderpane to threadpane
8. Arrowed down past the first thread to the second thread, intending to read
the first message.  The message body displayed, with the empty header.

There's a couple errors in the js console.  I don't know if the first one
happened when I selected the group in the folderpane, selected the message in
the threadpane, or at some other event altogether, but it sounds related:

Error: uncaught exception: [Exception... "Component returned failure code:
0x80550005 [nsITreeView.toggleOpenState]"  nsresult: "0x80550005 (<unknown>)" 
location: "JS frame :: <unknown filename> :: onxblkeypress :: line 6"  data: no]

Error: emailAddressNode has no properties
Source File: chrome://messenger/content/msgHdrViewOverlay.js
Line: 672

Comment 41

[K Chayka]

ack!  It happened again today on the 2002070204 build

1. Marked all read on the last group I'm subscribed to on secnews.netscape.com
2. Arrowed down the folderpane to the news.mozilla.org server
3. Clicked on twisty to expand the folder and update message counts
4. Arrowed down to the first group (n.p.m.builds, view is Unread messages only,
not threaded).  There were 2 messages in the threadpane.
5. Tabbed to the threadpane
6. Arrowed down to the first unread message - the body displayed, empty header

The same "emailAddressNode has no properties" error is in the js console.  The
error just before it is:
Error: can't decode principals (failure code 80004005)

I have no idea when that message appeared.

Comment 42

[laurel]

*** Bug 160484 has been marked as a duplicate of this bug. ***

Comment 43

[laurel]

*** Bug 160537 has been marked as a duplicate of this bug. ***

Comment 44

[Tony Mechelynck [:tonymec]]

Looks like this bug was last sighted in 2002.

Resolving WORKSFORME. If this bug bites you, please reopen.