Bug 191121

Summary:	css formatted html email doesn't color text correctly
Product:	[Applications] kmail	Reporter:	Gabriele Brosulo <gabriele.brosulo>
Component:	messageviewer	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	bjoern, christoph, michael.schramm
Priority:	NOR
Version:	1.9.10
Target Milestone:	---
Platform:	Slackware
OS:	Linux
Latest Commit:		Version Fixed In:

Description Gabriele Brosulo 2009-04-30 09:51:33 UTC

Version:           1.9.10 (using KDE 3.5.10)
Compiler:          gcc version 4.2.4 
OS:                Linux
Installed from:    Slackware Packages

just quoting Ingo replying to a kdepim-users question:

"KMail sets the color of the body text to black (or to whatever color you have defined in KMail/KDE as text color). When showing HTML messages 
then we should probably not force our text color on the HTML message."

Comment 1 christoph 2010-02-22 11:42:42 UTC

I can confirm this behavior. This still happens in Kubuntu 9.10 and the latest Kubuntu Alpha of 10.04

It is particularly annoying when reading newsletters.

Comment 2 Björn Ruberg 2010-02-24 23:56:39 UTC

Funny, this bug/feature was once requested in bug #126273

Comment 3 Michael Schramm 2010-02-25 09:13:26 UTC

#191121 is the same problem. Those emails assume that black is the font color and white the background, whereas the the default colors of the current skin might be the opposite.

as written in #191121 it would be nice if one could select own "default" colors for html mails, preset to something a newsletter would assume...

Comment 4 christoph 2010-02-25 10:18:07 UTC

Ok just to make this clear:

Changing the font-folor in mail texts for specific html elements works (with css or without it) - like spans, divs whatever.

What does not work is changing the text color of the body by using css.

i.e. body { color: #444 }

This makes no sense, and should be considered a bug and not a feature. 
Especially as you can change the background color.

Comment 5 Björn Ruberg 2010-02-25 10:27:30 UTC

When the problem is the overwriting of CSS definitions - than this is a duplicate

*** This bug has been marked as a duplicate of bug 129157 ***