Console error "closure invoked recursively or after being dropped" when executing navigate in a component using Indexed

[ab-honda-ichigo]

Describe the bug
When I run navigate, I get the error "Uncaught Error: closure invoked recursively or after being dropped" in the console.
This is reproduced in components using Indexed.

Oddly enough, this error always appears three times in the console, regardless of the number of Indexed items.

This can be avoided by providing an a element inside the li element and giving it the href attribute.
However, what I actually want to do is to implement an implementation that changes the destination according to the condition when the element is clicked, so I think it is necessary to use navigate.

To Reproduce
Below is the source code that this reproduces.

#[component]
pub async fn PopoverMenu<G: Html>() -> View<G>
{
    let items = create_signal(vec!["hoge", "fuga", "piyo"]);
    view!
    {
        ul
        {
            Indexed
            (
                iterable=*items,
                view=move |_|
                {
                    view!
                    {
                        li
                        (
                            on:click=move |_|
                            {
                                navigate("/");
                            },
                        )
                        {
                            "hoge"
                        }
                    }
                }
            )
        }
    }
}

Screenshots

Environment

• Sycamore: "0.9.0-beta.2"
• Browser: Chrome (Version 120.0.6099.224 (Official Build) (64-bit))
• OS: Linux (EndeavourOS, Kernel Version: 6.7.4-arch1-1)

Additional context
I found #433 as a similar issue.

[ichigo-dev]

Sorry, I'm the poster of this issue.
I posted with the wrong user, so I'll add a comment to receive a notification.

[lukechu10]

The issue has something to do with the fact that the element is removed when the event handler is executed. When the element is removed, the event handler is dropped while it is running! It is indeed the same issue as #443 #433 but I think we can leave this open since it provides a good test case for it.

Edit: referenced wrong issue.

[ichigo-dev]

Thank you for your detailed explanation.
Sorry for the trivial point, but the related issue is #433, not #443.