Closed Bug 275858 Opened 20 years ago Closed 19 years ago

Lost alternating colors in Received Messages

Categories

(SeaMonkey :: MailNews: Message Display, defect)

1.7 Branch
x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: bcook, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041217
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041217

I have had many versions of mozilla/firefox/thunderbird installed on this box.

I have uninstalled all of them, and removed directories where I could find them.
 Recently I installed Moz 1.7.5 for someone and noticed somethings about their
Received message window that was different from mine.

They had alternating colors for the messages, and I do not.

Again I uninstalled my 1.7.5 version and removed the directories, and
re-installed 1.7.5 and still no alternating colors.

I have 3 imap accounts on this install and one pop3 and two smtp authentication
setups.  When I go to compose new message, the From drop down just lists the
'Your Name' field that is populated under each account; again on the new install
of 1.7.5 that I did for someone else it listed the name and email address and
account (some of it was in a lighter grey and italics)

I use the smoke theme and just got the latest version from spuler.us; it didn't
make a difference.

I'd like to know what I can do to make those settings come back :)

It seems mozilla has no problem overwriting my prefs.js when it comes to things
like the 'Side Search Box' :) (which I keep having to disable after each install.)

Whatever I can do to help please let me know, b/c I have this same thing
happeneing on my other win2k box at work.

Again, several revs of moz suite have been installed on that box, and it just
seems that I don't have all the latest little features; but I do have 1.7.5
installed.

Reproducible: Didn't try

Steps to Reproduce:
1. Install 1.7.1
2. Overwrite install with 1.7.2
3. Overwrite install with 1.7.3
4. Overwrite install with 1.7.4
5. Overwrite install with 1.7.5

Actual Results:  
I did not actually do this before I submitted this bug.  But this is the way
that I feel it happened.

Expected Results:  
I feel that mozilla should have updated my setting where it could or notify that
it needed to do a merge on some settings.  Or at least something telling me that
might not have something and possibly how I might need to manually merge some
settings on my own.. something more than nothing would be nice.
Version: unspecified → 1.7 Branch
Assignee: sspitzer → mail
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/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.