Closed Bug 86683 Opened 23 years ago Closed 23 years ago

Mail headers don't display in Message window

Categories

(SeaMonkey :: Build Config, defect, P1)

x86
All
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 86737
mozilla0.9.2

People

(Reporter: esther, Assigned: leaf)

References

Details

(Keywords: regression, smoketest)

Using windows build 2001-06-18-09 and the 2001-06-19 the mail message headers
don't display in the message pane.  This started with the 6-18-09 build.  Also,
the start page for Mail is the mozilla mail and news url.   

1. Install the 6-18-09 build
2. Launch an existing or new profile
3. Open Mail and notice the start page location is the mozilla mail and news url.  
4. Click on a mail message in thread pane 

Result: The message displays in the message pane but the heard isn't there. 
Resizing and moving the grabber doesn't bring the header out.  Clicking through
messages will eventually bring out a thin header column with the Attachment
icon, but you can't see the message header.
Haven't checked Mac and Linux yet.
cc'ing mscott.  This appears to have started happening on the 6/18 release build
and still happens on the 6/19 1am build.
Priority: -- → P1
Target Milestone: --- → mozilla0.9.2
message pane --> me
Assignee: sspitzer → mscott
this usually means someone introduced a JS error during mailnews startup which
prevents the message header sink from gettinging installed on the message pane.
I bet it's commercial only too.
Mac build 2001061908 does not have the problem
Linux build early on 200106-18-06 does not have the problem, but since it's an
early build it may not have had the problem.  I fail at installing the other
6-18 linux builds and the 6-19 linux build so I can't check them.  
Argh! This bug was filed five times!
*** Bug 86682 has been marked as a duplicate of this bug. ***
*** Bug 86684 has been marked as a duplicate of this bug. ***
Hmm, I can't seem to reproduce this using the 2001061804 windows build and my
debug commercial build from this morning doesn't show it either. Strange.
Putterman, your comments made it sound like you see this behavior too?
*** Bug 86685 has been marked as a duplicate of this bug. ***
*** Bug 86686 has been marked as a duplicate of this bug. ***
Sorry for all the duplicates, there was no response when I clicked the Commit
button while logging the bug, I found out the password dialog was up behind the
bug page, as soon as I dismissed it the bug committed.  There may be 4 or 5
duplicates.  
I found four duplicates and have marked them as such. I guess the QA Contact for
the duplicates will have a tedious time verifying them. Oh, that's you, Esther! ;-)
I don't see this on my 200161823 win98 commercial build, or my own linux debug
mozilla build
I downloaded the 2001-06-19-11 build and still see the problem.  Note: the
6-18-07 build did not have the problem the 6-18-09, 6-19-01, 6-19-11 all have
the problem.    Scott did see the problem too.  I was in his cube when he tried
one of the bad builds.  
esther & scott, can you guys try on a new profile to see if that fixes it for you?
New profile has the problem too.  Also note, with commercial build new profile I
didn't get the activation window.  Suzanne logged 2 bugs for Activation and IM
windows not coming up, this bug is probably related to those bugs 6581 & 6573.
I also can't make this work with a new profile.  It's a commercial problem.  All
of my prefs are defaulting to mozilla preferences (mail start page, forwarding
as attachment, etc).
Adding smoketest and regression keywords.  Is this problem related to the other 
bugs I have seen during my smoketesting, including no activation screen, no aim 
setup dialog and search not working (bug 86737)?
*** Bug 86747 has been marked as a duplicate of this bug. ***
Yup, I think they are all related Jay. I bet overlays or something similar broke
in the commercial tree. 
Ok, I can see this on a release build from the 19th now. 

According to the JS console, it seems that every time someone in the commercial
tree trys to read a bool pref, we are throwing an exception. Maybe the
commericial init .js files are no longer getting packaged correctly?
Yup, we are definetly no longer able to read out commercial only default prefs.
It throws an exception every time. If I manually add some of these prefs values
in my prefs.js file then thinks start working right away. 

So now is it a packaging problem that prevents aim.js, mailnews.js and other
commercial prefs files from getting loaded or is it an implementation change.....

This would also explain why there is no activation happening on new profiles and
other things. The pref for kicking off activation never gets read in.
This is most definetly a packaging problem. I just looked in the dist directory
of my release build and under bin\defaults\pref, none of the commercial prefs
files are present. Only the mozilla ones (mailnews.js, all.js, etc). 

cc'ing some installer folks who might be able to help me figure out why.
Sean helped me look into this and it turns out it's a release problem. His
installer build from noon today properly includes the commercial preferences
files  in the release build it generates so the bug isn't in the installer.
Ergo, it must be a release bug. Sean mentioned something about some changes to
delete CVS folders which happened recently in the release process. Maybe that is
causing the problem? We should look on the build machine to make sure in
bin/defaults/prefs we have our commericial js files.

Over to leaf!
Assignee: mscott → leaf
the change i made shouldn't be selectively removing some commercial files, but 
not others. I'll take a look at the release machine when it finishes up its 8pm 
build.
Status: NEW → ASSIGNED
the files that are missing on the ns side are bin/defaults/pref/*-ns.js.  These 
get packaged up fine (into browser.xpi) on my debug build that was pulled around 
noon today.
ok, i'm flummoxed. When i run the commands the automation runs, the right .js 
files get exported to the installer-stage; continuing the search for why they 
aren't there when the automation runs.
Component: Mail Window Front End → Build Config
Product: MailNews → Browser
resolving as a dupe of the bug that was moved to bugscape

*** This bug has been marked as a duplicate of 86737 ***
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
verified
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.