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
As the title says, there are cases where content is replaced entirely, but the components initial loader on mount still exists, and therefore triggers multiple times, and then behaves unexpectedly because of sudden multiple triggers on non-existent elements in the DOM.
Current fixes
// Bail early if node doesn't exists anymoreif(!document.body.contains(node)){return;}
The text was updated successfully, but these errors were encountered:
As the title says, there are cases where content is replaced entirely, but the components initial loader on mount still exists, and therefore triggers multiple times, and then behaves unexpectedly because of sudden multiple triggers on non-existent elements in the DOM.
Current fixes
The text was updated successfully, but these errors were encountered: