wallabag
Previous/next article buttons do not work when filter by tag is active
If i have a list of articles, which i filter by a tag, then i open an article in the middle of the list. The previous and next button do not work with the filter then. They show the next/prev. article by date, but not from the filtered list but the list of all articles.
I also doubt these buttons make any sense anymore. I would like to remove them. If i scroll to the end of an article, i'll usually use the mark as read button. And this one moves me back to the article list after i push it. So the prev./next buttons are never used and clutter the interface only.
I have tested it. I am not experiencing any such problems. In a list filtered by a tag, the navigation buttons appear at the end as normal and work perfectly. It navigates to the next article exactly as in the corresponding filtered list
Only for the last article in the list does the next-button lead back to the unfiltered list But I think that's fine.
I use the app, where it is sorted by creating date by default https://github.com/wallabag/android-app/pull/1161#issuecomment-2936754475
The list filtered by tag needs to filter in the way, that the article before and after one selected article is not the same as in the full list. I mean, if we have five articles: A, B, C, D, E and then we filter by tag, the filtered list should have e.g. A, C, E. Then i open article C and push "previous". In the app it opens article B then, but i would have expected it to open article A.
edit: I also use the current master version a1aee09cb029d518e18844f2e53cd38092635c84
It was just a coincidence that it worked for me. Articles are often saved one after the other under one tag (on one topic).
I checked it again thoroughly. You are right! After the filter with a tag, the next and previous buttons no longer work as expected.
In the end, the bug does not bother me, because i do not ever use these buttons. I used them only to test the PR you mentioned above. That is why i saw this bug only now.
I would vote for removing the buttons, because IMO there is no use case for them.
I usually use the back button in the status bar at the top. That takes me back to the overview.
Maybe this bug can be easily fixed by the developer. I don't mind the next and previous buttons and i actually find the "mark as read" button quite useful I'm not sure whether the other buttons should be removed altogether, so I would like to abstain from voting.
i actually find the read button quite useful
Same for me. This one is essential. Only the prev/next buttons are superfluous