Closed Tsourdox closed 6 years ago
Hm, sorry about that! Thanks for the heads-up!
Don't have a ton of time on my hands for this ATM, PRs welcome!
i'll take a look at it at the end of the week. might also use it to do some dom cleanup, which hopefully prevents some more edge cases with nodes not being removed
tested this in chrome/ff/ie11 with v2.10.1 as well as 2.9.1 . handler is being invoked correctly.
@Tsourdox if the problem persists, im going to need a reproducable code snippet (for example a codesandbox)
I believe I tested it in Safari but I'll se if I can test it again and se if the issue was on my behalf.
safari (11) works as well:
Tested it and it doesn't fire in any browser. I'm using FlipMove together with react-dnd but even if I remove that code the problem persists. I'll try and update to the latest version and se if that changes anything. At the moment I don't need the event so I'm good for now. Thx for looking in to it!
Ok then, closing this issue. It could be a problem with another library stopping propagation of events, but i'm just speculating here. If you manage to reproduce the problem, just reopen it.
This is how I'm using it.
[onStart, onStartAll, onFinish] works as expected. Using version 2.9.1