Dominic Gannaway

@mimbrown Yes, you need to flush everything. If you have a parent `{#if}` block, which is just an effect under the hood, and you have a sync effect inside that...

I wouldn't consider this a bug, but given that Svelte 4 would patch mismatches from SSR HTML (such as the table case), and we no longer do that in Svelte...

Unfortunately, we have to do this as Svelte doesn't use a virtual DOM, so it doesn't know that the DOM structures for both are the same/similar. Making this change would...

I'm not really sure how valuable this is outside of maybe optimising for specific known constants like `DEV` and `BROWSER`. If we output the condition before the block, we also...

> > I'm not really sure how valuable this is outside of maybe optimising for specific known constants like `DEV` and `BROWSER`. If we output the condition before the block,...

> Unless we remove the function call and just compile to if-else? You need to show me an example, I'm struggling to see how that would work.

> I'd love to see this tackled before a full Svelte 5 release. I'm obviously an outsider who isn't aware of all the intricacies of the Svelte compiler, but as...

@dummdidumm I don't see how this PR can fix that issue? I'll look into it tho

It was a perf opportunity. I’ve had bigger fish on my radar though so feel free to take over or close

> With newest Svelte 5 version - flickering is no more visible. > > But! If you click faster than animation duration - you will see strange effect where elements...