After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 269995 - Evolution ignoring <font face> markup in HTML messages.
Evolution ignoring <font face> markup in HTML messages.
Status: RESOLVED WONTFIX
Product: GtkHtml
Classification: Other
Component: Rendering
3.8.x
Other All
: Normal normal
: Future
Assigned To: gtkhtml-maintainers
gtkhtml-maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2004-11-29 01:24 UTC by Rich Renomeron
Modified: 2014-12-02 01:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Rich Renomeron 2004-11-29 01:24:01 UTC 
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:

In Evolution 2.0, display of HTML messages uses the "default" font, even if
another font is specified in the HTML, either by <font face=""> or CSS.

Steps to reproduce the problem:
1. Make sure default message font is something other than Georgia.
2. Open HTML message with <font face="Georgia"> markup. 

Actual Results:

Message displayed with default font.

Expected Results:
Comment 1 Radek Doulik 2005-03-31 17:37:22 UTC 
gtkhtml now ignores font face's => rescheduling for 2.3 work
Comment 2 André Klapper 2006-01-10 02:00:21 UTC 
retargetting from 2.3 to 2.5
Comment 3 André Klapper 2006-08-22 17:19:00 UTC 
removing old target milestone.
Comment 4 Matthew Barnes 2008-03-11 01:03:10 UTC 
Bumping version to a stable release.
Comment 5 André Klapper 2014-12-02 01:06:36 UTC 
Since version 3.6, Evolution uses WebKit instead of GtkHtml for displaying messages. (And for completeness, Evolution 3.14 is planned to use WebKit also for composing and editing messages so GtkHtml will not receive any fixes anymore.)

Hence I am closing this GtkHtml rendering bug report.
We are sorry that your request was not handled in time when it was reported but unfortunately manpower is very limited (and does not allow testing every single reported issue separately again either).

Please feel free to reopen this report (and move it to the "Evolution" product and the "Mail" component) if the problem described in this bug report still happens in a recent supported Evolution version which uses WebKit (the current stable Evolution version is 3.12).