On <http://sports.yahoo.com/> and sub-pages, there are horizontal scrollbar glitches, where a scrollbar is drawn at the bottom of the page (perhaps unnecessarily), and then when you scroll down in the page, the scrollbar becomes detached from the bottom and appears in the middle of the page content.
Steps to Reproduce:
(1) Launch Safari 3.
(2) Empty cache.
(3) Open http://sports.yahoo.com/
(4) At the top, click on "Tennis".
(5) Scroll down the page.
The scrollbar becomes detached from the bottom of the window, appearing in the middle of the page content and moving up as you scroll down.
A scrollbar should not appear in the middle of the page content.
Build Date & Platform:
Safari Version 3.0.4 (523.12.2) on Mac OS X 10.4.11 (Build 8S2167).
Additional Builds and Platforms:
WebKit revision 30511 built from source and using the run-safari script.
The appearance of the visual glitch seems to depend very much on the window size. If the window is too small, it will not appear. Also, the glitch may not appear when loading the page subsequent times, so you may need to empty the cache to reproduce.
I've attached three screenshots. The file yahoo1.jpg shows the page after you first load, with the scrollbar on the bottom. The file yahoo2.jpg shows the page after scrolling down, and you can see that the scrollbar has moved up. The file yahoo-TOT.tiff shows a visual glitch with extraneous scrollbar widgets; you can see them on the right side of the screen between the game scores and the vertical scroller.
Created attachment 19298 [details]
Screenshot after page load
Created attachment 19299 [details]
Screenshot after scrolling down
Created attachment 19300 [details]
Screenshot using WebKit revision 30511
This bug may be a duplicate. There are a number of bugs that seem similar, but there wasn't one that stood out as being an exact duplicate.
I can still reproduce this with Safari 3.1.1 (4525.18). However, I haven't been able to reproduce it yet with WebKit revision 34478.
I haven't been able to reproduce this bug for a very long time, so I'd say it's fixed.