Steps to reproduce this bug: 1. Navigate to http://www.kotaku.com 2. Take a look at the left sidebar, as well as where it meets the bottom of the page. So, for some reason, the sidebar gradient-thing gets replicated *behind* (on the z-axis) where it's supposed to be, a number of pixels to the right (less in shipping Safari, more in ToT Webkit). Not only that, but the sidebar graphic where it's *supposed* to be doesn't extend all the way to the bottom of the page, while the replicated and misplaced version of said graphic actually does. Since this error is present in both Safari and nightly Webkit, it isn't exactly a regression, though the problem is more pronounced in the nightlies. Page renders fine in Firefox. Screenshots to come.
Created attachment 12681 [details] Correct rendering in Firefox (2.0.0.1) Notice the single sidebar gradient, its placement relative to the left and bottom edges of the page, and its non-intrusion into article text. This is (one would assume) how it's supposed to look.
Created attachment 12682 [details] Less-bad misbehavior in shipping Safari (2.0.4/419.3) Note, in addition to the sidebar weirdness, the existence of a scrollbar for no apparent reason.
Created attachment 12683 [details] More-bad misbehavior in Webkit nightly (r19136) More sidebar weirdness, and more scrolling. Just bigger and more noticeable than before.
Confirmed difference to Firefox 2.0.0.1 with locally-built debug build of WebKit r19151 with Safari 2.0.4 (419.3) on Mac OS X 10.4.8 (8N1037).
Huh. So I just viewed the page with r19524, and it looks fine. So either the bug was fixed very recently (within the past day or two) by some other change, or the website itself was altered to display better. Investigating.
After testing with released Safari (2.0.4/419.3), it appears that the site's layout was tweaked. So, it wasn't any change to Webkit that got it fixed. :/
(In reply to comment #6) > After testing with released Safari (2.0.4/419.3), it appears that the site's > layout was tweaked. So, it wasn't any change to Webkit that got it fixed. :/ Please consider saving a webarchive (or a "Web Page, Complete" from Firefox) when this happens. Usually that's enough to reproduce the issue later, although note that neither Safari nor Firefox do a good job of saving @import-ed CSS files, images references from CSS files, or dynamically added script/style elements. To make sure the issue is reproducible, disconnect all network connections and then load the webarchive or the web page, complete.
Nothing to work with here unfortunately. Closing.