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

[sgalzin]

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

[Danish Hakim]

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