Bug 368101 - Doesn't show Amazon e-mail
Summary: Doesn't show Amazon e-mail
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: gtkhtml3
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-06 11:06 UTC by Bastien Nocera
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-11-06 14:23:00 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
amazon-email.txt (16.42 KB, text/plain)
2007-11-06 11:06 UTC, Bastien Nocera 		no flags Details
Screenshot-INBOX.png (13.13 KB, image/png)
2007-11-06 11:07 UTC, Bastien Nocera 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 494170 0 None None None Never

Description Bastien Nocera 2007-11-06 11:06:53 UTC 
evolution-2.12.1-3.fc8
gtkhtml3-3.16.1-1.fc8

Evolution doesn't show any text or images when loading this e-mail from Amazon.
Comment 1 Bastien Nocera 2007-11-06 11:06:53 UTC 
Created attachment 248941 [details]
amazon-email.txt
Comment 2 Bastien Nocera 2007-11-06 11:07:52 UTC 
Created attachment 248951 [details]
Screenshot-INBOX.png

What shows up in Evo
Comment 3 Matthew Barnes 2007-11-06 12:42:16 UTC 
I see that too.  Looks like Evolution (or GtkHTML) is having trouble with the
text/html part of the message.  If you switch to "Prefer Plain" you can at least
read the text/plain part.

  Edit -> Preferences -> Mail Preferences -> HTML Messages -> HTML Mode
Comment 4 Milan Crha 2007-11-06 14:23:00 UTC 
I never saw such an ugly formatted HTML page, never ever. Maybe I didn't see
enough yet. They should try to validate it with W3C validator, because the <BR>
is not a pair element, as far as I know... 
Nevertheless, moving upstream [1] and attaching patch for gtkhtml there.

[1] http://bugzilla.gnome.org/show_bug.cgi?id=494170
Note You need to log in before you can comment on or make changes to this bug.