Closed Bug 112591 Opened 24 years ago Closed 16 years ago

Hardwired color in message headers (link readability deps on sys colors)

Categories

(SeaMonkey :: Themes, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: hramrach, Unassigned)

References

Details

Note: report as I could not find any Themes/Skins section in MailNews. Version: 0.9.6 Win32 Mail messages are displayed with page background background and system foreground. Consider system colors such as yellow on green or white on darkgray while default page colors are black on white. Mail header links are blue in Classic skin (consider not so unlikely blue system background)
Whiteboard: DUPEME
*** This bug has been marked as a duplicate of 69436 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Background is covered in bug 69436, narrowing desc to links only. Adding ui since it is in bug 69436 too. Seeing on Linux with 0.9.8 -> changing os to all
Status: RESOLVED → UNCONFIRMED
Keywords: ui
OS: Windows NT → All
Resolution: DUPLICATE → ---
Summary: Readability of mailmessages depends on system color → Hardwired color in message headers (link readability deps on sys colors)
Whiteboard: DUPEME
Reporter (hramrach), please can you check to see whether this bug is still present in a recent build (Moz1-RC1 or a new nightly build). If this bug does not occur please can you resolve it worksforme.
Still seen in 2002-04-22-07 on Linux
and the same story again: Reporter (hramrach), please can you check to see whether this bug is still present in a recent build (moz1.1beta or a new nightly build). If this bug does not occur please can you resolve it worksforme.
I can still see this in 11b on Linux with Classic. Some headers of mail messages are blue ignoring system colors. The problem is probably in the Classic theme because the headers have different color in LCARS. The solution for button text on toolbar which had the same problem some time ago was to display in text color. Can at least anybody else see the problem?
I tried the following: I set system color (KDE) for links to some fancy green. The links in the header pane of mail messages were still blue. Is this what your bug is about? pi
No IMO KDE has nothing to do with Mozilla colors at all. IIRC Mozilla on Linux uses GTK colors for Classic skin (Netscape 4 used X resources which could be set form KDE). There is probably no link color in GTK but you can change background/foreground (ie to yellow on blue). Mozilla with Classic skin changes background/foreground but the links in mail headers are always blue. The same problem is on Windows except Windows system colors are used.
I'll confirm this. This is caused by the following code in /classic/skin/messenger/messageHeader.css /* ::::: msg header email addresses ::::: */ .emailDisplayButton { cursor: pointer; color: #0000FF; text-decoration: underline; margin: 0; } .emailDisplayButton:hover { color: #FF0000; } It is generally considered bad UI to mix system colors and absolute colors. The fix there should simply be to remove the lines containing color, since text-decoration: underline; takes care of that need. If you look at IE Skin at http://mozillako.hypermart.net/ieskin/ you will notice that the message header links are identifiable as a links even without the color.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Blocks: 112580
This looks like a dup of bug 63809 (Message display background color ignores preferences)
No, that bug is about document area, this is about headers. The problem is similar but different. I agree that underlining of headers should be enough since I do not know any color that is safe to use except the text color.
Product: Core → SeaMonkey
Assignee: hewitt → nobody
QA Contact: pmac → themes
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: 24 years ago → 16 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.