You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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 theli
element and giving it thehref
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.
Screenshots
Environment
Additional context
I found #433 as a similar issue.
The text was updated successfully, but these errors were encountered: