Most recent hoverIntent initialisation break previous ones.
roydukkey opened this issue · comments
HoverIntent blows away all previous initialisation.
Ooh, yeah, that's a bug, and possibly the same as (or maybe at least related to) #28.
My guess is that it's because the timeout ID is stored on the element, which means it can be unexpectedly overwritten if hoverIntent was invoked more than once on the same element... I'll take a look. Thanks for reporting it!
After finally having some time to look further into this, I can confirm that the bug is indeed a result of how certain state information is stored per-element when it really should be per-instance-per-element. (Also it's completely unrelated to #28.) Fix forthcoming!
@roydukkey would you care to take a look at #39 and see if it fixes your problem (and doesn't cause new ones)? Feel free to leave comments on the pull request.