Open ALJCepeda opened 2 months ago
Hi, can you create a much more minimal reproduction, possibly in the REPL ? The more minimal the reproduction is the more is possible that the bug is actually in svelte and not in application code (and the easier would be to find the root cause and fix it).
@ALJCepeda gave it a shot (but you should make a StackBlitz/ SvelteLab demo)
In /test/[id]/+layout.svelte
you forgot a '$':
- windowW >= screenSizes.sm}
+ $windowW >= screenSizes.sm}
... but I narrowed it down to an issue with <slot/>
in this component, i.e. doing this temporarily won't freeze things:
{#if loggedIn && windowW}
{#if $windowW >= screenSizes.sm}
<!-- <DesktopLayout>
<slot />
</DesktopLayout> -->
foo
{:else}
<!-- <slot /> -->
bar
{/if}
{:else}
<Spinner size={150} />
{/if}
Update: given that <slot/>
was an issue I narrowed it down further to FullScreenDrawer.svelte
in the +page.svelte
, specifically something's borked with the 'wrapper' class.
Describe the bug
Hello everyone!
This is is my first time reporting a bug to a major framework like Svelte so please show me some patience..
After playing around with it in the debugger and inspecting the components.. it seems like a second reactive context is created for the
Conversation
component but it fails to mount properly as it's stuck in this infinite rendering.. and so any updates to the store causes the other reactive context to spit off another update and the two contexts ping pong back and forth between each other causing an infinite loop in the rendering!Why does this only happen if the resolution is above 768 px?
Reproduction
https://github.com/ALJCepeda/svelte-bug
Logs
No response
System Info
Severity
annoyance