-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Transition prevents {#if}{:else}{/if} from being exclusive #3410
Comments
I think this is a related issue to what I have found. With mine, the text on the first if statement remains until the prior element has finished the transition. Expected behavior |
Fixed in 3.21.0 - https://svelte.dev/repl/c902889c05814dd69198661ad49030e1?version=3.21.0 |
I still got this issue using SvelteKit. It happens when a nested component has any kind of out transition. |
I notice this as well in svelteKit, I had to use some annoying boolean logic to work around it (set a separate variable to true when the transition is complete and use that to display the |
Same problem here with sveltekit |
I ran into this with |
Also seeing this with SvelteKit |
This bug is still present as of
Super annoying bug-- it took me hours to track down that it was a transition like 5 layers of heirarchy below an |
Describe the bug
A transition deep within some components makes both the true and false parts of an if/else render on the page.
To Reproduce
If you remove
transition:slide
fromScaffold.svelte
the problem is no longer there.Expected behavior
I expect either the true or the false sections of the if statement to show, not both at the same time.
Information about your Svelte project:
Your browser and the version: Firefox
Your operating system: macOS
Svelte version: I don't know? Whatever the REPL is running?
Whether your project uses Webpack or Rollup: Rollup
Severity
Mildly annoying. I'll remove the transition for now, but would love to be able to use transitions when I release the production app.
Additional context
I'm a newbie and very impressed with Svelte.
The text was updated successfully, but these errors were encountered: