Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calling Toast.dismissAll() a second time without any new toasts triggers error "_this29.el.parentNode is null" #6674

Open
sgalzin opened this issue Oct 19, 2022 · 1 comment

Comments

@sgalzin
Copy link

sgalzin commented Oct 19, 2022

When calling Toast.dismissAll twice, an error is generated: "_this29.el.parentNode is null"

Expected Behavior

I expect the second call should notice that the elements have already been marked for clearing and not generate an error when the dismissal actually tries to access those previously cleared elements.

Current Behavior

Triggers an error when trying to clear previously cleared elements.

Steps to Reproduce (for bugs)

see codepen: https://codepen.io/sgalzin-the-vuer/pen/ExLBxwM?editors=0010

  1. call toast();
  2. call dismissAll twicebefore the toast has had time to expire.

Your Environment

Firefox and Chrome on Ubuntu

@Jerit3787
Copy link

Hi, this project is no longer maintained! The community-managed fork is still being maintained. Please open an issue there instead. Thanks! https://www.github.com/materializecss/materialize

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants