Widget re-renders on HTMX cached page, duplicating content

[gone]

load a page, x-widget will render a component successfully. If you click a link with https://htmx.org/docs/#boosting (or any htmx request really, but boosting is easiest to imagine) applied to it, htmx will cache the page you're currently on and move forward (https://htmx.org/docs/#history). If you then hit back, htmx restores the cache and then x-widget renders the component. This will cause a nested effect with two renders of the component.

Here's an example of the first navigation or loading the page directly

And after clicking a boosted link and hitting back:

I know I hit you with a bunch of bugs all at once, if you provide some high level guidance on how you'd like me to take a shot at them I"m happy to take a crack.

[gone]

Actually - in this specific component I have two slots, one that is named and one that isn't

The duplicated content is in the UNNAMED slot only - the top level named slot is empty.

If I add a name to the unnamed slot, the same behavior gives two empty slots

[allain]

Interesting. Wouldn't this behaviour happen with plain old alpine too?

[gone]

Yeah possibly - I'll do some experimentation over the weekend