Do scroll to top of post if no comment is selected.
It turns out that if the user reads a lot of comments, then scrolls
back to the top of the post, the user cannot easily read the post
again. We simply don't scroll in that situation.
We want to keep from scrolling in the situation where the users
requests more comments when in the middle of reading some. But not
when they scroll off the top.
Issue #28., Let users loop through loaded comments.
When visiting a post, p will go to the last loaded comment. When
visiting the last loaded comment, n will go to the top of the post.
Issue #29., Let users loop through loaded posts.
On initial load, no post is selected, and j would take the user to
the first post. Now, in that state, k will take the user to the
last post. While on the first or last post, they will go to the
opposite end (unlike comments, which will take the user back to the
containing post). A little bit inconsisent, but I think appropriate.
One current problem is, when visiting the last post, it will often the
UI to load more posts. This loading will interfere with keeping the
current post in view. This problem exists else where as well, so a
common solution will be needed. However, once posts are loaded,
navigating up or down then back will get to the correct post.
Issue #29., Let users loop through notifications.
Closes #29.
