Transitions break basic functionality

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:

{#if condition}
   <Child/>
{/if}

…where the <Child/> is using transitions.

Reproduction: https://svelte.dev/repl/2e801ddf39f646709a3aa1b74f727f71?version=3.6.5

Instructions (also included in the REPL):

1. Click the button to show the child component
2. Write something in the input to reveal (with an animation) the close-button
3. Click the close button and observe how the app breaks (not closing the child component)

[RedHatter]

I made a minimal repel and traced down the problem.

During the outro svelteIsBroken is updated causing the update function of the fragment to be called which in turn calls transition_in on the if block ending the outro before it’s able to remove the component.

p: function update(ctx, [dirty]) {
	if (/*show*/ ctx[1]) {
		if (if_block) {
			if_block.p(ctx, dirty);
			transition_in(if_block, 1);
                ....

i: function intro(local) {
	if (current) return;
	if (div_outro) div_outro.end(1);
	current = true;
},

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.

[Conduitry]

This appears to still be present in 3.6.6.