You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A clear and concise description of what the bug is
Simple example:
<script>
import { page } from"$app/stores"
</script>
{$page.route.id} <<<<---- this line change when route change
<AppShell>
<HeaderzIndex={101} slot="header"height={60} fixed>
your header content
{$page.route.id} <<<---- this line is not changing when route change
</Header>
<NavbarhiddenBreakpoint={'sm'}
slot="navbar"fixed
>
your navbar content
</Navbar>
<ShellSectiongrow>
<slot />
</ShellSection>
</AppShell>
In which browser(s) did the problem occur?
No response
Steps To Reproduce
Import page from "$app/stores"
Use the following property of page : $page.route.id inside <AppShell /> (Preffer use inside <Header /> or <Navbar /> sections)
Make two differents routes
Navigate between both routes
The $page.route.id will not change in
Do you know how to fix the issue
No
Are you willing to participate in fixing this issue and create a pull request with the fix
No
Relevant Assets
bug.mp4
(Watch the behaviour of the red and green boxes when the route changes)
The text was updated successfully, but these errors were encountered:
!Update
I found a temporal fix to ignore this problem:
Use the following svelte directive:
{#key$page.url.pathname} <--- using the `key` directive to fix the bad behaviour with `AppShell`
<AppShell>
<HeaderzIndex={101} slot="header"height={60} fixed>
...
</AppShell>
{/key}
What package has an issue
@svelteuidev/core
A clear and concise description of what the bug is
Simple example:
In which browser(s) did the problem occur?
No response
Steps To Reproduce
page
from "$app/stores"page
:$page.route.id
inside<AppShell />
(Preffer use inside<Header />
or<Navbar />
sections)$page.route.id
will not change inDo you know how to fix the issue
No
Are you willing to participate in fixing this issue and create a pull request with the fix
No
Relevant Assets
bug.mp4
(Watch the behaviour of the red and green boxes when the route changes)
The text was updated successfully, but these errors were encountered: