-
-
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
[Svelte 5] {#if}
block with several reactive children does not re-render properly
#12230
Comments
Hey @dummdidumm thanks for working on this, I just bumped to 168 and the bug is still happening |
(me referencing that issue was a mistake, this bug seems unrelated) |
You managed to reproduce! I failed doing so without Kit |
It turns out the bug is still there, but instead of not displaying the content of the Recording.2024-07-01.210516.mp4I can try creating a repro in the REPL if it helps. The exact code is the following: |
@GauBen Have you tried the latest version? A REPL link would be preferable too :) |
Yes, I bumped to 5.0.0-next.169 and instead of not showing after the first toggle, it fails after the second toggle |
@GauBen Is it the same in dev and prod? |
Just tried, it behaves the same in dev and prod |
If that helps:
Update:
|
Here is a stackblitz of the issue https://stackblitz.com/edit/sveltejs-kit-template-default-mhzb7t?file=src%2Froutes%2F%2Bpage.svelte,package.json Can you please re-open? |
Also works when replacing |
Thanks for all the hard work Svelte team! |
Describe the bug
Given the following
+page.js
:And a
+page.svelte
:Clicking Open event will show a title and a body, clicking Close will close it, clicking Open event again will do nothing.
Very small changes can make it work:
<p>{event.body}</p>
will fix the issue$inspect(event)
will fix the issue(This is likely to be a quatum physics issue given that observing the behavior changes it 😂)
Reproduction
https://stackblitz.com/edit/sveltejs-kit-template-default-mhzb7t?file=src%2Froutes%2F%2Bpage.js
Logs
No response
System Info
Severity
blocking an upgrade
The text was updated successfully, but these errors were encountered: