keyboard navigation doesn't work as I'd expect
j and k, rather than going to the post before or after the currently expanded post, go to the post before or after the post that is currently at the top of the page.
When viewing posts in list form, I expect navigation to work in relation to the currently expanded post. As it is, if I scroll the page at all, j and k work in a suprising and not totally predictable way.
-
Eugene Kenny commented
This is still a problem. Digging around in the site's JavaScript, it looks like all keyboard shortcuts are implemented in terms of the window's current scroll position: https://gist.github.com/eugeneius/5941855 (note the copious use of scrollTop()).
This might make sense for "full view", where all posts are expanded and the scroll position is the best way to determine which article the user is currently reading. But in "list view", one post is explicitly expanded, and any actions taken should be relative to that post.
-
Mike Castle commented
I think with the recent UI refresh, this is working as expected now.
-
Xavier Jackson commented
I want to say that at one point J navigated to the next post, which is what its listed function is in keyboard shortcuts. but now k works as expected and j is barely functional simply opening the current post.
-
Nathan Baker commented
I agree completely!