Bug 159476 - Foreground color always set to black (instead of KDE-default) when not defined by Webpage
Summary: Foreground color always set to black (instead of KDE-default) when not define...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (show other bugs)
Version: 3.5
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-17 16:47 UTC by Paul
Modified: 2012-06-18 17:24 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Html Snippet (90 bytes, text/html)
2008-06-26 02:30 UTC, Steve Hay
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Paul 2008-03-17 16:47:27 UTC
Version:           3.5.8 (using 3.5.8, Kubuntu (gutsy) 4:3.5.8-0ubuntu3.3)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.22-14-generic

THIS BUG IS NOT A DUPLICATE OF 47320!

A Webpage like this one:

<html> 
<head><title>Test1</title></head>

<body>
F00 Bar F00 Bar F00 Bar 
</body>
</html> 

is never readable when the KDE-wide Background is set to black (no matter which foreground color is set).
When a webpage does not define a foreground or a background color you should EXPECT that the KDE-wide settings are used. In my case this should be red text on black background, i know of many other people using white text on black background. However Konqueror sets the background color (which is NOT overridden by the website) to the KDE-default (black) and sets the foreground color (which is also NOT overridden by the website) also to black (which is NOT the KDE-default). The result is a website which you cannot read despite the fact that neither my personal color scheme nor the color scheme of the website are wrong. Of course all this would not be your fault if the website would override the color scheme, but it doesn't, so it is your fault. 

THIS BUG IS NOT A DUPLICATE OF 47320!

This bug has been around since 2004 now and several reports were closed and ignored since then. The bug is still existing.

THIS BUG IS NOT A DUPLICATE OF 47320!

To fix this bug it is only necessary to use the KDE-default color and to override this color setting ONLY if another setting is requested either by the website or by a user defined css. This is exactly the behaviour a user would expect and it is not what Konqueror currently does.

THIS BUG IS NOT A DUPLICATE OF 47320!

It is NOT an acceptable workaround to use a user defined css sheet because this would override the color settings of ALL websites, also those which define individual and useful colors.

Please do not close this bug-report until the bug is fixed.

THIS BUG IS NOT A DUPLICATE OF 47320!

Thank you for FIXING this bug, and please remember:

THIS BUG IS NOT A DUPLICATE OF 47320!
Comment 1 Paul 2008-03-17 16:57:26 UTC
Oh, and please dont hesitate to send me a mail if you do have any questions or if it seems to you that this is a duplicate of 47320 (which it is not).
Comment 2 Steve Hay 2008-06-26 02:30:25 UTC
Created attachment 25611 [details]
Html Snippet

From bug report.
Comment 3 Steve Hay 2008-06-26 02:33:02 UTC
Able to reproduce svn 823139.  Forwarded for developer attention.
Comment 4 Maksim Orlovich 2008-06-26 02:35:13 UTC
Yeah it does something pretty bizarre in the code, which I can't recall right now (came from a discussion with someone else). But reporter, please layoff the caps, will ya?
Comment 5 Paul 2008-06-26 16:30:11 UTC
Yeah you are rigth, I wasn't really in the mood to be polite when i first wrote the report. It really sucks when you want to report a bug and find that it has already been reportet several times and the problem is not going to be fixed because someone keeps claiming that the bug doesn't even exist. I'm still using Konqueror and I really like the browser.
Comment 6 Maksim Orlovich 2008-06-26 17:20:52 UTC
Actually what you reported is pretty much the -opposite- of the previous thing. But heck, no big deal, tempers happens --- as do mistakes in classifying bug reports.
Comment 7 Hohyeis 2012-02-22 10:16:56 UTC
There was another bug report for this bug. It might have been pulled in from a previous bug tracking database. It was also on the most frequently reported duplicates list. Have old bug reports been erased? This report can now be marked as confirmed.
Comment 8 Janek Bevendorff 2012-06-18 17:24:04 UTC
Message from the Bugsquad and Konqueror teams: This bug is closed as outdated, as we do not have the manpower to maintain the KDE3 version anymore. If you still can reproduce this issue with Konqueror 4.8.4 or later, please open a new report. Thank you for your understanding.