The back button does not work since the update to v2.1.0

[ogarcia]

Steps to reproduce it:

1. Go to any feed where there is more than one article to read.
2. Read the first article.
3. Press the next button to read the next article.
4. You can't press the previous button because it doesn't work.

This happens regardless of how you have sorted the items (older or newer first).

[fguillot]

I think you are referring to this pull-request https://github.com/miniflux/v2/pull/2138 that was made to fix this issue https://github.com/miniflux/v2/issues/1212.

Basically, the default behavior has been changed to circle through unread entries. In that context, the previous link will always be disabled because the previous entry has been read.

Clicking on "show all entries" button should give you back the previous behavior.

Relevant XKCD: https://xkcd.com/1172/

[ogarcia]

IMHO in a reading session you should be able to navigate back and forth as you could before. There are multiple reasons for this, for example you are using the keys and unintentionally double click on next. Or you are reading a feed with a lot of articles and you want to go back to one that you found interesting.

Navigating using all articles is impossible in feeds with a large number of articles. Especially since it is not possible to switch between "unread" and "all articles" within the reading panel of the same article. For example a newspaper feed can easily reach 2K articles and and if you read them in chronological order, when you switch to "all articles" you can easily have the first 1900 articles already read.

Wouldn't it be possible to keep the previous functionality as a configuration option? For example something like.

Back / Next default behavior

• Unread
• All articles

[juanbretti]

Wouldn't it be possible to keep the previous functionality as a configuration option?

Or changing the navigations buttons to something like: << Previous read Next unread >>

And when all the entries are read, the text should change to: << Previous read Next read >>

Considering the previous: something to have in mind, the swipe action (on mobile) should or should not be limited to show previously read entries? Or when coming from an unread entry list process, the swipe action is limited to only unread. And requires the manual click to move to a previously read entry.

[juanbretti]

A workaround is instead of trying to use the disabled << Previous, is to use the browser back button (or keyboard shortcut Alt + Left Arrow).

[juanbretti]

Is it being considered to make some changes to this behavior? Thanks!