Closed as not planned
Closed as not planned
Description
Describe the bug
I've found two bugs with navigating using both goto
and pushState
related to $page
store.
When navigating with goto
to the same route as the current one even though $page.state
changes no $effect
runs on it.
When using pushState
and passing new url to it you get stuck with $page.params
pointing to the previous incorrect url.
Reproduction
Here is the repo: https://github.com/gyzerok/sveltekit-nav-bug
Bug with goto
and state:
- Go to page
/bug
- Click
goto
button - No effects run and console log anything (expected console log about state change)
- Click
Log $page
button and see that actually state in the $page changed
With Svelte I strongly expect that if some state changes the effects are run as a result of this change which is not the case here.
Bug with pushState
and url:
- Go to page
/bug
- Click on
pushState
button - You get a log where
params.id: "bug"
, however in the browser url you see/test
Logs
No response
System Info
@sveltejs/kit: 2.6.1
svelte: 5.0.0-next.260
Severity
serious, but I can work around it
Additional Information
No response