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 625956 - Amazon home page rendering problem
Amazon home page rendering problem
Status: RESOLVED INVALID
Product: banshee
Classification: Other
Component: Other Extensions
git master
Other Linux
: Normal normal
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-08-03 16:34 UTC by Robin Stocker
Modified: 2010-08-04 07:39 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
rendering problem (157.96 KB, image/png)
2010-08-03 16:34 UTC, Robin Stocker 		Details
JavaScript errors (1.17 KB, text/plain)
2010-08-03 16:35 UTC, Robin Stocker 		Details

Description Robin Stocker 2010-08-03 16:34:44 UTC 
Created attachment 167056 [details]
rendering problem

When opening the Amazon home page by clicking on the Amazon source, the page has rendering problems (see screenshot).

It doesn't matter if I'm logged in or not, but it only happens on the home page of Amazon (home icon). On the "my account" page, the rendering is fine.

Switching to amazon.com (as opposed to .de), the proplem is still there.

Some JavaScript errors are printed on the console (see attached log). They only happen when browsing to the home page and not with the "my account" page, so they might point to the problem.

I'm using libwebkit 1.2.3 from here: https://launchpad.net/~webkit-team/+archive/ppa

Banshee from git: 8cfbadba1853fdf29f5d2f68f55974b866e063b2
Comment 1 Robin Stocker 2010-08-03 16:35:21 UTC 
Created attachment 167057 [details]
JavaScript errors
Comment 2 Robin Stocker 2010-08-03 16:38:21 UTC 
One thing I forgot: It's possible to just scroll down. After the many repeated Amazon logos, the actual content starts and from there to the end of the page it looks fine.
Comment 3 Robin Stocker 2010-08-03 16:40:19 UTC 
One more thing (sorry): I'm using Banshee behind a proxy.
Comment 4 Aaron Bockover 2010-08-03 17:05:00 UTC 
Well, we don't do anything to modify the site. It's just running as it should be inside WebKit. Do you get this problem in Epiphany (built against the same WebKit)?

What happens if you turn off proxy support?

We use the GNOME+SOUP proxy feature the same way as Epiphany, so, nothing special there AFAIK.
Comment 5 Robin Stocker 2010-08-04 07:39:21 UTC 
It looks normal in Epiphany.

I just tried it again in banshee, and today it looks fine. So maybe it was just the proxy having a bad day. Sorry about that.