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 603269 - epiphany 2.28.1 renders Lenovo USA site garbled
epiphany 2.28.1 renders Lenovo USA site garbled
Status: RESOLVED DUPLICATE of bug 522772
Product: epiphany
Classification: Core
Component: General
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-11-29 00:09 UTC by Albert Hopkins
Modified: 2009-11-29 21:08 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Screenshot of epiphany acting crazy on a web page (291.91 KB, image/png)
2009-11-29 00:09 UTC, Albert Hopkins 		Details
lenovo usa (231.92 KB, image/png)
2009-11-29 14:55 UTC, Fabio Durán Verdugo 		Details

Description Albert Hopkins 2009-11-29 00:09:52 UTC 
Created attachment 148671 [details]
Screenshot of epiphany acting crazy on a web page

Whenever I to to Lenovo USA site I get garbled non-textual output.  However I was able to go to the site fine prior to the 2.28 series.

http://www.lenovo.com/us/en/

See the attached screenshot.
Comment 1 Fabio Durán Verdugo 2009-11-29 14:42:32 UTC 
with chrome this is not reproducible, only with epiphany, I can confirm this, I'am sure I saw a similar bug, but i cant found
Comment 2 Fabio Durán Verdugo 2009-11-29 14:55:00 UTC 
Created attachment 148689 [details]
lenovo usa

as I change the preferences, and check "web inspector" in the general tab, and fonts and Style, check "Let the page specify their own fonts" and "Let the page specify their own Color" ant this problem is solve for me
Comment 3 Reinout van Schouwen 2009-11-29 21:08:51 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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