-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transitions break basic functionality #3202
Comments
This appears to still be present in 3.6.6. |
If the I'm not sure what this indicates. |
Still present in 3.16.7 |
I made a minimal repel and traced down the problem. During the outro
I've made a few simple attempts to solve it without success. I'm not sure how to fix this short of disabling the outro's ability to be canceled all together. @Conduitry Any ideas? Or should we give Rich a ping? Edit: I should mention that this issue is a blocker at my work. |
Would a basic fix then be to not use any |
I believe that the fix is the same as the fix for https://github.com/sveltejs/sapper/issues/814 where transitions break Sapper's routing. The solution is to use the
Updated working repl is here - https://svelte.dev/repl/8bfae7a0389d42f09087298b2e621fd9?version=3.19.2 but also works on 3.6.5. |
Fixed in 3.21.0 - https://svelte.dev/repl/2e801ddf39f646709a3aa1b74f727f71?version=3.21.0 |
Sorry for the vague title. It's late.
Using transitions seems to break basic functionality in some circumstances. By basic functionality I mean a simple
if
clause in the template, like so:...where the
<Child/>
is using transitions.Reproduction: https://svelte.dev/repl/2e801ddf39f646709a3aa1b74f727f71?version=3.6.5
Instructions (also included in the REPL):
The text was updated successfully, but these errors were encountered: