You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 16, 2020. It is now read-only.
I am not so sure that is always true. I have a "deals" folder where I subscribe to slickdeals.net and spoofee deals. These RSS feeds are one line articles where all the information is in the article. For that scrolling every time making it harder to track visually.
I would propose that if the article doesn't fit or takes up more than 50% of the screen then it should scroll to the top.
There's some sense to that, although I'd probably set the cutoff lower than 50%.
There's a specific failure case that keeps hitting me, though:
* You have an article that's longer than a page.
* You hit space some number of times to see the rest of it.
* The next article appears at the bottom of the page, partly shown.
* You hit 'j', expecting it to move to the top.
* Instead, that article gets skipped entirely, and the third article appears at the top.
I believe this happens because GoRead marks the second article as read as soon as it appears. I think that's the wrong behavior; if it just delayed that marking until the next 'j', it would probably just work.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
No description provided.
The text was updated successfully, but these errors were encountered: