Closed Bug 151881 Opened 23 years ago Closed 15 years ago

Mail Message List and Sidebar doesn't honor background color setting

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: markus, Unassigned)

References

(Depends on 1 open bug)

Details

When setting the background color via Edit/Preferences/Appearance/Background, it is only honored by the message pane, but not by the side bar and the message list (Verified with 1.0 under Linux and Windows 2k).
Confirming this is still broken with mozilla 1.2.1 - Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 Although from reading other people's comments on other bugs, perhaps this is a theme problem? I can't check without restarting the browser and losing all my current pages [I'm suffering a "bookmark tabs doesn't work; crashes mozilla instantly" bug] :( (stupid design to have to restart anyway, if bugs can depend on your current theme!) but I'm uaing the theme: "aquaMOZ".
Have now restarted, and confirm I am getting this bug independent of theme used (I still get it e.g. in the Classic theme). Mozilla 1.2.1 as stated before.
What I am seeing with 1.4b, for the mail/news tree and thread pane, and for the sidebar, is that the Classic theme now honors the system colors (rather than forcing black-on-white), but does not follow the Preference setting, which appears to be reserved for content. With the Orbit theme, the non-content panes are black-on-white; content panes follow the preference. I would think a theme could be developed that would follow the preference.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Depends on: 178003
This is a superset of bug 103455.
*** Bug 206942 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Assignee: mail → nobody
QA Contact: olgam → message-display
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
I downloaded latest seamonkey, 2.0.4. After six years nothing changed. I can configure message background and cannot configure background of folder list and message list. It is on Linux RH 5.3, x86. In thunderbird those colors are configurable either, but at least in message list half of lines are not of bright write color. Need other help to check colors? Need a screenshot?
As Mike pointed out seven years ago: > the Classic theme now honors the system colors (rather than forcing black- > on-white), but does not follow the Preference setting, which appears to be > reserved for content. This is still true and working as designed. You can change the colours by either using a different theme or by overruling them in your userChrome.css file.
Resolution: EXPIRED → INVALID
You need to log in before you can comment on or make changes to this bug.