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

Tusky doesn't properly keep timeline position #1516

Closed
mhellwig opened this issue Oct 3, 2019 · 3 comments
Closed

Tusky doesn't properly keep timeline position #1516

mhellwig opened this issue Oct 3, 2019 · 3 comments

Comments

@mhellwig
Copy link

mhellwig commented Oct 3, 2019

I use Tusky. I scroll along my timeline. I switch to another app, keep the phone in my pocket for a while, I re-open Tusky. Expectation: I see the same Toot that I saw when I had Tusky open the last time. Reality: I see some random other, newer Toot and have to scroll down and search until I find my position again. This works with other apps (e.g. fedilab, which I want to move away from for other reasons)


  • Tusky Version: 9.1

  • Android Version: 8

  • Android Device: Moto Z play

  • Mastodon instance (if applicable):

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

@charlag
Copy link
Collaborator

charlag commented Jan 14, 2020

Duplicate of #1443

@charlag charlag marked this as a duplicate of #1443 Jan 14, 2020
@charlag charlag closed this as completed Jan 14, 2020
@mhellwig
Copy link
Author

Please reopen, it is not a duplicate of the other issue. I have the phone orientation locked to portrait, so there is no orientation change, it just randomly happens on some updates (but not all).

I have now experienced cases where the "jump to later position" happened while I was reading the timeline. I didn't even touch the screen, tusky did an automatic update of the timeline and Bam, 30 toots or so forward while I blinked. definitely no orientation change while that happened.

@charlag
Copy link
Collaborator

charlag commented Jan 14, 2020

I linked wrong issue, sorry,
it's a duplicate of #89

@charlag charlag marked this as not a duplicate of #1443 Jan 14, 2020
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

2 participants