Closed Bug 78394 Opened 23 years ago Closed 23 years ago

Mozilla ignores color preferences

Categories

(SeaMonkey :: Preferences, defect)

x86
All
defect
Not set
minor

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 77828

People

(Reporter: togdon, Assigned: mcafee)

Details

I've set Mozilla to use alternate standard colors for links, text, and page
backgrounds. These had been working through the 20010426 linux build. 

Since then all pages that don't explicitly declare colors through either style
sheets or body tags have had grey backgrounds, black text, blue unfollowed
links, and purple followed links (pages that declare colors are working fine). 

Blowing away my preferences by deleting the .mozilla directory didn't seem to
help. I'm seeing this up through todays build.

I figured that someone would have reported this bug by now (I absolutely hate
purple followed links, and I want to think that others do too...), but searching
turned up nothing. I may just be missing it, but if so the summary for that bug
needs the word color(s) in it.
Confirming on 2001043004 Win2k, setting OS to All.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Just remembered bug 69436 says about the same thing regarding to mail/news (but
system colors were proposed as a solution). The only thing changed since then is
that hardcoded white turned to hardcoded gray. Is this a general issue affecting
both browser and Mail/News?
> Is this a general issue affecting both browser and Mail/News?

Yes. I'm seeing it in mail too (although I don't actually use Mozilla for mail).
Just opening up a message in composer used to follow my prefs, now it's set at
the old defaults. 


dup.

*** This bug has been marked as a duplicate of 77828 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
mass verification of duplicate bugs: to find all bugspam pertaining to this, set
your search string to "DuplicateBugsBelongInZahadum".

if you think this particular bug is *not* a duplicate, please provide a
compelling reason, as well as check a recent *trunk* build (on the appropriate
platform[s]), before reopening.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.