Yes, it breaks it. Items are marked as read when cursor goes through them. But after selecting item in the middle of the screen cursor doesn't go up. So only items below are marked as read.

I know it isn't good solution. But I can't yet come to better one that will satisfy all users.

This change completely breaks the Mark Read On Scroll Feature.
If I open item #20, then PAGE scroll, items 1-19 aren't marked Read !
Am I missing something ?

This is 90% and works for me. I'd rather the cursor never change -- since I sometimes overscroll, and don't expect a cursor change -- but I can live with this. Thanks!

I'm struggling now with keyboard navigation with this change ... trying to move item focus !
j/k insist on opening items and up/down doesn't move focus
and could my mouse scroll difficulties be down to use of page scroll rather than line scroll ?

would it be possible to just have an option for this to satisfy this request ?
I find the way it works at the moment is perfect - I can see no logic in scrolling down a list and having the focus lost somewhere a few screens back ?

@Ah! puzzled ... yes the former exactly, just opened an item and 18 previous items won't mark as read

Are you're opening some items and items above aren't marked as read or it doesn't mark items as read even if you're not opening them?

AH! puzzled over last couple of days why scrolling pages have not been marking items as read on feeds with more than a page of items - maybe 50% only of items working at best sometimes only 10% marked read !
Windows7/Firefox/MS Intellimouse

Yes, collapsed list view item has the same behavior as before when cursor goes down. Only expanded list view item locks cursor till item goes out of screen.

Works for me, thanks! I notice that the "cursor" jumps to next article as soon as the previous article's top touches the top of the screen.

This is really the only reason I don't use BazQux. Vladimir has been relentlessly improving this service, but I just can't find it usable for me. I'm using Feedbin right now, and would probably switch over to BazQux the second this has been addressed.

Please implement this..

This issue is especially annoying when I hit 'g' and Readability opens another article instead of current.

Cursor keys also should not move the focus. This is very inconvenient: you hit "down" to continue reading a long article, then you hit "j" or "space" to go to the next article, and suddenly it turns out that the focus was already on the next article. Or you use mouse wheel and the focus is on some random unpredictable article. We have j/k, n/p and space buttons to move the focus, this is how it worked in Google Reader.

Maybe this problem is specific for list view.

As long as this still allows to mark articles read by just scrolling through the article list...