When scrolling past the last article in the reading list the entire page scrolls rather then just scrolling up the last article. The entire UI then remains moved up the page with white space at the bottom. Once scrolling to the top of the reading list the UI again scrolls back into the correct position.
See attached screen shots.
Created attachment 13679 [details]
Google Reader Rendered Normally
This attachment shows Google Reader when the page is rendered correctly. It also shows the result of scrolling back to the top of the reading list once the entire UI scrolled up leaving white space at the bottom.
Created attachment 13680 [details]
Google Reader Scrolled Up Incorrectly.
This attachment is a screen shot of the entire Safari Window. The white space at the bottom is displayed incorrectly when scrolling past the last article in the reading list. Once the reading list is scrolled to the top the white space disappears. You will notice that the grab handle in the bottom right corner is moved up by the white space at the bottom.
This is a Reader issue (that we'll be fixing), not a WebKit one.
Per Comment #3, this is a Google evangelism issue.
The problem has now been fixed in Reader.
Is this the annoying bouncing left pane issue? When I scroll down the left pane bounces up and down a number of times and then finally settles down. I am using the released version of Safari on a PowerPC.
No, it doesn't bounce (at least for me). It simply jumps straight back to the top.
Also, when using the latest build on 10.5.2, the key commands seem to be mixed up. I cannot use the Page Up/Down, Home/End, or the directional keys to scroll down the different feeds like I used to. The only thing that works is the Space Bar. "J" seems to act like the Down key, "K" for up, "S" adds a star to the article, "A" opens up an "add subscription" box, "E" opens an email box, "M" marks the article as read/unread, "R" reloads the feeds, "U" opens the subscriptions box, "F" opens up a "Friends' Articles" page, and "/" tabs to the search bar. That's all I've found so far. I'll keep looking for more. Hope this gets resolved soon as I use Google Reader as my main RSS app between my MBP and iPhone and since Webkit seems so much snappier than regular Safari.
Any of these issues still occurring in Google Reader?
The original issue was fixed on the Reader side long ago (see comment 4), and I was not able to reproduce the issue mentioned in comment 9.