-
Notifications
You must be signed in to change notification settings - Fork 87
Library screen - Recyclerview repositioning issues [Sir Black Energy, Cat Knight] #452
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
Comments
RobbWatershed
added a commit
that referenced
this issue
Jan 17, 2020
…y far without reason after going back from the image viewer
Part of the issue --> mikepenz/FastAdapter#861 |
Codename Liza |
RobbWatershed
added a commit
that referenced
this issue
Jan 20, 2020
- Use commons-lang3.ImmutablePair instead of Pair to avoid null check warnings
RobbWatershed
added a commit
that referenced
this issue
Jan 20, 2020
RobbWatershed
added a commit
that referenced
this issue
Jan 21, 2020
… to the screen after LibraryActivity has been destroyed and recreated (#452) - Cleanup
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current behaviour
Variant 1
On some phones, the library activity will be killed while the user uses the image viewer (brutal memory optimization ?).
As a consequence, when going back to the library activity, the list may not remember its position (item 0 of current sorting is displayed on top of the screen).
Variant 2
When going back to the library screen from the image viewer, the main list sometimes "teleports" to position (number of books per page x2).
Expected behaviour
Even when killed under pressure, the library activity should remember its exact position of the list when going back from the page viewer
See https://stackoverflow.com/questions/52587745/how-to-save-and-restore-scrolling-position-of-the-recyclerview-in-a-fragment-wheThe text was updated successfully, but these errors were encountered: