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

Bug: Multiple notifications, throws failed to execute 'removeChild' #13

Closed
Fredrik-Oberg opened this issue Oct 1, 2016 · 3 comments
Closed

Comments

@Fredrik-Oberg
Copy link
Collaborator

To reproduce :

  • Open two notifications
  • Close one of them manually

image

@trevor-atlas
Copy link

Any more details on reproducing this? I was unable to do so on latest chrome.

@Fredrik-Oberg
Copy link
Collaborator Author

@trevoristall In latest Chrome,

  • open one 'success' and one 'warning'
  • close 'success' before it auto closes
  • wait for 'warning' to auto close

@Fredrik-Oberg
Copy link
Collaborator Author

After some more investigation it can be reproduced by just opening any and then close it.

When the event mouseleave triggers it creates a new timeout.
Could be that the event mouseleaves is triggered when we close the notification and it is animated down. Thus creating a new setTimeout, but the DOM element is already removed when that timer has run out.

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

No branches or pull requests

2 participants