Replies: 1 comment
-
Nevermind, found the |global parameter for transitions, which was what I was looking for :) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi community,
trying to "play" with transitions like fade or fly and came across following situation:
My test project has following routes:
Every route has a +layout.svelte file.
[id] as well as [action] folder have transitions in their +layout.svelte files.
Now lets imagine I visit my link /12345/confirm and use a backlink to /12345, the transition of my [action] (confirm) layout file is finished correctly, before navigating to /12345.
Now I stuck with a problem, if I jump from "/12345/confirm" back to root "/".
The transition of [id] is fired before [action] transition even starts or finishes.
After [id] transition finishes, [action] transition doesn't even fire, instead it jumps directly to root / and content of [action] layout disappears without transition.
Probably I don't understand the concept of transitions, or transitions purpose isn't for such use case.
To my question: Is it even possible to chain transitions like if i call / from /[id]/[action], transition are done in order of [action] -> [id] -> / root ?
Beta Was this translation helpful? Give feedback.
All reactions