A leak is occurring with repeated use:floatingContent.

[sinbino]

This is a slightly modified version of an example from the document.

<script lang="ts">
  import { offset, flip, shift } from "svelte-floating-ui/dom";
  import { createFloatingActions } from "svelte-floating-ui";

  const [ floatingRef, floatingContent ] = createFloatingActions({
    strategy: "absolute",
    placement: "top",
    middleware: [
      offset(6),
      flip(),
      shift(),
    ],
    onComputed() {
      console.log('😡 onComputed!')
    },
  });

  let showTooltip: boolean = false;
</script>

<div style="height: 2000px">
  <button
    on:mouseenter={() => showTooltip = true}
    on:mouseleave={() => showTooltip = false}
    use:floatingRef
  >Hover me</button>

  {#if showTooltip}
    <div style="position:absolute" use:floatingContent>
      Tooltip
    </div>
  {/if}
</div>

Repeat hover to repeatedly create and destroy the DOM containing the use:floatingContent. Then onComputed is verbosely called depending on the number of times the DOM is regenerated.

Is it possible that when the DOM containing the use:floatingContent is destroyed, the floatingContent is not properly cleaned up after?

[sinbino]

In svelte-floating-ui/src/lib/index.ts, line 75, the return value of initAutoUpdate seems to expect a cleanup function, but the _autoUpdate function has been processed inside the tick promise, I think it is not passed to autoUpdateDestroy.

[fedorovvvv]

Hii
Thank you for that 🧡
I'm updating the library to the latest versions and this fix will be in an upcoming release