Closed Bug 295840 Opened 20 years ago Closed 19 years ago

text rendering broken or unable to display when background is changed on a page

Categories

(Core :: Layout, defect)

x86
All
defect
Not set
major

Tracking

()

RESOLVED INVALID

People

(Reporter: diffie, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050512 Firefox/1.0.4 (Dropline GNOME)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050512 Firefox/1.0.4

On http://marc.theaimsgroup.com/?l=linux-kernel default bacground is black with
white text but upon change of the bacground to white and text to black the
hyperlinks or text on webpage is no longer rendered or seen.

Reproducible: Always

Steps to Reproduce:
1.go to http://marc.theaimsgroup.com/?l=linux-kernel
2. scroll down and hit Configure
3. select lists.kde.org (black on white) theme
4. hit Go to the Lists link

Actual Results:  
The black text is not visible on the hyperlinks etc...only the bold text is seen

Expected Results:  
Firefox 1.0.4 should have rendered the page correctly.

This behaviour does not happen on Mozilla Firefox 1.0.3 version. Firefox is used
on Slackware 10.1 with GNOME 2.10.1 and was built with GTK+2/XFT support.
I see this also with 
Mozilla/5.0 (Windows; U; Windows NT 5.2; de-DE; rv:1.8b2) Gecko/20050526
Component: General → Layout
OS: Linux → All
Product: Firefox → Core
QA Contact: general → layout
Version: unspecified → Trunk
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050528
Confirmed using Suite Trunk Nightly 2005052805 on Windows XP.
From the (white) page:

<body bgcolor="#ffffff" text="#000000" link="#ffffff" vlink="#800080">

The color of links (and of the backgrownd) is specified as "#ffffff" - i.e.
white. So the browser is just doing what it's told.
Verified that it looks like this in Safari as well.
Yep.  Just as server bug -- it claims to update the link color to #0000C0 but
actually doesn't.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.