Closed TERRORW0LF closed 1 hour ago
I can only reproduce this if navigating to a page that 1) uses Suspense, but where 2) the navigation is immediately-ready (i.e., I remove the delay in the api.rs
functions).
Is this the case for you? If not, could you provide a reproduction rather than the steps to reproduce based on the router
example? I can probably fix this but I want to make sure it addresses your actual issue too.
Describe the bug When navigating to a nested route neither the browser's url nor the page get updated when using a RoutingProgress in the app. Clicking the link to the nested route again displays the correct page. The same thing happens on the first navigation inside the nested route.
Leptos Dependencies
To Reproduce Steps to reproduce the behavior:
cargo leptos watch
about
sectioncontact
sectionExpected behavior The navigation to the nested route completes after the first link click.