Bug 13425 - Google Reader doesn't scroll to reveal an article opened using a keyboard shortcut
Summary: Google Reader doesn't scroll to reveal an article opened using a keyboard sho...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 523.x (Safari 3)
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Nobody
URL: http://reader.google.com/
Keywords: GoogleBug
Depends on:
Blocks:
 
Reported: 2007-04-20 17:50 PDT by Adam Roben (:aroben)
Modified: 2007-11-10 14:24 PST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Roben (:aroben) 2007-04-20 17:50:22 PDT
Google Reader doesn't scroll to reveal an article opened using a keyboard shortcut

Repro steps:
1. Have a long list of articles in Google Reader (long enough that you have a scroll bar)
2. Click on the first article
3. Type 'j' repeatedly until you reach articles off the bottom of the screen

Results:
The article list should scroll to reveal the opened article, but doesn't. If you click on an article, it does scroll (though you might run into bug 13423)
Comment 1 Tommi Komulainen 2007-05-04 14:21:01 PDT
From what I can tell this broke between r13058 and 13060.

Unfortunately at the same time 13060 broke reader differently (fails to display subsciption titles) until somewhere between 13265 and 13372 so I can't trace this more accurately.
Comment 2 Tommi Komulainen 2007-05-12 22:24:41 PDT
On further bisection I think this broke with the fix for bug 7108. r12659 works, 12660 doesn't.

Instead of 'j' I'm using 'n' to avoid marking articles as read, should be the same bug though.
Comment 3 Mike Aizatsky 2007-06-05 04:37:34 PDT
This is indeed very annoying and is the only reason I still run shipped Safari.
Comment 4 Tommi Komulainen 2007-06-22 07:15:44 PDT
In r23558 any of the keys besides Space don't seem to be doing anything.
Comment 5 Adam Roben (:aroben) 2007-11-10 14:24:50 PST
This now works for me. It may have been fixed on Google's side.