Closed Fredrik-Oberg closed 8 years ago
Any more details on reproducing this? I was unable to do so on latest chrome.
@trevoristall In latest Chrome,
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.
To reproduce :