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

[BUG] Feed List reloads to top when switching between tabs #34

Open
boscojwho opened this issue Jul 20, 2023 · 4 comments
Open

[BUG] Feed List reloads to top when switching between tabs #34

boscojwho opened this issue Jul 20, 2023 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@boscojwho
Copy link
Contributor

Describe the bug
Scroll down main Feed list, then switch to another tab (e.g. Inbox), then switch back to Feed. Feed will do a fresh reload and start from the top.

To Reproduce
Steps to reproduce the behavior:

  1. Load main Feed and scroll down a few pages.
  2. Switch to another tab (e.g. Inbox).
  3. Switch back to Feed.
  4. Feed reloads to top.

Expected behavior

  • Feed should stay where it was without loading.

Information:

  • Version 0.1 (1)
@boscojwho boscojwho added the bug Something isn't working label Jul 20, 2023
@Athlon007
Copy link
Owner

Is there even a way to keep the position of a Feed, when switching between pages, without having it in memory at all time?

@boscojwho
Copy link
Contributor Author

Is there even a way to keep the position of a Feed, when switching between pages, without having it in memory at all time?

Not really, some parts of it will have to remain in memory, but this isn't an uncommon pattern (keeping multiple pages in memory).

But while thinking about this problem, I started wondering whether it might make more sense if Feed, Inbox, and Search should live in a system TabView, instead of being in the sidebar? Apollo did this on iPhone, and many other Lemmy apps also use the same pattern. Using a tab view would have the added benefit of not having these three pages reload when switching between them.

@Athlon007
Copy link
Owner

Alright, but I want to do it after the release of 0.2 (probably this Monday/Tuesday). I want to release 0.2, see if people encounter bugs, and release potential 0.2.1.

I will have limited time to work on Leomard from 29th July to 12th August, and ESPECIALLY I won't be able to work on it between 4th and 10th :)

@boscojwho
Copy link
Contributor Author

Woohoo, 0.2 lets go =P

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Bugs
Development

No branches or pull requests

2 participants