Skip to content
New issue

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

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

Already on GitHub? # to your account

Framework7 Svelte: Root page disappears on navigate back #4293

Open
erskingardner opened this issue Oct 10, 2024 · 2 comments
Open

Framework7 Svelte: Root page disappears on navigate back #4293

erskingardner opened this issue Oct 10, 2024 · 2 comments

Comments

@erskingardner
Copy link

erskingardner commented Oct 10, 2024

I'm posting here because the forum is blocking all new #s from all IP addresses.

I'm using framework7-svelte and have a page with several views (one that is set as the main view) and then pages that are loaded via routes (think whatsapp style messenger that navigates from a chats page, into a chat, and then clicking on the nav bar goes into a profile page).

  • I can navigate to a chat and back to the chats list (main view) without trouble.
  • I can navigate between tabs without trouble
  • The issue is that when I go from chats list -> chat -> chat info -> chat -> chats list. The last step animates the chat page out and shows the chats list page for a fraction of a second before completely disappearing.

There are no console errors and I can see that the page events are firing, the UI is just not being rendered properly.
I've also added console logs on each route change and logged out the full route params, nothing seems amiss here. There's no difference in the params from when the page loads initially vs when it disappears.

Any ideas?

@Muhammed-Rahif
Copy link

Muhammed-Rahif commented Oct 25, 2024

I am also facing this issue after migrating to svelte 5. @erskingardner can you confirm which version of svelte are you using? If svelte 5, then this is probably related svelte 5 and a migration will be appreciated!

@erskingardner
Copy link
Author

I'm using svelte 5. In the end I restructured my app a bit and added some time delays in the navigation and the problem went away.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants