Bug 815690 - Incorrect HTML message formatting
Incorrect HTML message formatting
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
17
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-24 05:29 EDT by Mikhail
Modified: 2012-04-25 05:46 EDT (History)
3 users (show)

See Also:
Fixed In Version: evolution-3.5.1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-04-25 05:46:39 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
example message (5.67 KB, application/mbox)
2012-04-24 05:29 EDT, Mikhail
no flags Details
Outlook - right formatting (63.38 KB, image/png)
2012-04-24 05:30 EDT, Mikhail
no flags Details
Evolution - wrong formatting (67.89 KB, image/png)
2012-04-24 05:30 EDT, Mikhail
no flags Details

  None (edit)
Description Mikhail 2012-04-24 05:29:09 EDT
Created attachment 579798 [details]
example message

Description of problem:
Incorrect HTML message formatting
Comment 1 Mikhail 2012-04-24 05:30:08 EDT
Created attachment 579799 [details]
Outlook - right formatting
Comment 2 Mikhail 2012-04-24 05:30:52 EDT
Created attachment 579800 [details]
Evolution - wrong formatting
Comment 3 Milan Crha 2012-04-25 05:46:39 EDT
Thanks for a bug report. The GtkHTML widget is used to render messages in 3.4.x (and earlier), but it doesn't understand Cascading Styles within HTML messages, where your message uses it to draw message text in red. Current development version of evolution uses WebKitGtk instead of GtkHTML, which understands this kind of stuff very well. This version will be released next Monday, as 3.5.1, but it's a development version, which will become 3.6.0 after few months, and then it'll get to Fedora 18.

Note You need to log in before you can comment on or make changes to this bug.