Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

always load new posts in the same direction #2496

Closed
1 task done
spicewiesel opened this issue May 3, 2022 · 3 comments
Closed
1 task done

always load new posts in the same direction #2496

spicewiesel opened this issue May 3, 2022 · 3 comments

Comments

@spicewiesel
Copy link

After refreshing the "Home" tab new posts are shown above the current position.
Posts loaded using the "load more" button are then shown below the current position.

That frequentially leads to a situation where I have new posts to read above and below my current position and that's quite confusing.

Expectation: Always put new posts in the same direction. If the reading direction (new posts on top or bottom) is configurable the loading direction could be dependend on that.


  • Tusky Version: 17.0

  • Android Version: 12

  • Android Device: Pixel 5

  • Mastodon instance (if applicable): toot.berlin

  • I searched or browsed the repo’s other issues to ensure this is not a duplicate.

@68kmentat
Copy link

I believe that the "load more" button is supposed to load in either direction, depending on whether it is in the top half or the bottom half of the screen. That may still be confusing for users but I personally appreciated that function.

It actually hasn't been doing that for me since a recent update, I came here to find out if the change was intentional or a bug

@spicewiesel
Copy link
Author

Personal preferences aside I don't see the benefit from positioning new posts in two different directions, having new posts below and above your current position. It just breaks the flow of reading.

@charlag
Copy link
Collaborator

charlag commented May 10, 2022

I believe this is a duplicate of #2423

@charlag charlag closed this as completed May 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants