• Jan 28, 2018

    v1.8.3

    v1.8.3 (for npm)
    Supersedes the unauthorized 1.8.x versions previously published to npm.
    
    Please note that this is functionally equivalent to the official
    versions 1.8.0 and 1.8.1 found on GitHub.
    
    Addresses #67.

v1.9.0

@usmonster usmonster released this Sep 4, 2017

  • Refactored plugin to fix a long-standing bug (#35) that prevented multiple hoverIntent instances to be active on the same element. (#39)
  • Exports plugin as an AMD module so it can be used with AMD loaders. (#33)
  • The pageX and pageY properties of the event passed to the "over" handler now reflect current mouse position. This makes it easier to implement common behaviors with hoverIntent, such as tooltips. Please note that this may be a breaking change for some; if your "over" handler requires the unmodified coordinates from original mouseover, you can still read them from the event.originalEvent. (#11, #49)
  • Documentation has moved to github.io. (#47)
  • Many other improvements and bug fixes.

Once again, many thanks to the GitHub community for your bug reports, improvement suggestions, and PRs.

v1.8.1

@usmonster usmonster released this Aug 22, 2014 · 22 commits to master since this release

Minor update: fixes bower.json to indicate that the plugin works with all versions of jQuery >= 1.9.1.

v1.8.0

@usmonster usmonster released this Mar 16, 2015 · 25 commits to master since this release

  • Changed to Semantic Versioning (e.g., from r8 to v1.8.0) (83d2877)
  • Removed errant U+FEFF character from beginning of JS file (09215ef)
  • Renamed jQuery variable to $ for consistency (avoids possible name collision) (#15)
  • Changed mouse movement measurements to use euclidean (instead of rectilinear) distance (#14)

Thanks to the GitHub community for patches, suggestions, and fixes!

v1.7.0

@usmonster usmonster released this Mar 16, 2015 · 37 commits to master since this release

  • Enables event delegation via new selector configuration option
  • Adds hoverIntent namespace to mouse events when attaching handlers, providing better isolation
  • Invoking with a single function will cause it to be used as the handler for both "in/over" (mouseenter) and "out" (mouseleave) intents.