- Breaking: Dropped support for IE 11
- Fix: Use
event.target
in cases where the target has been removed from the DOM (#17). Thanks @sgparrish.
- Fix broken urls to hammerjs in examples.
- Switched from
hammerjs
to@egjs/hammerjs
because the former is not actively maintained. Thanks @mojoaxel. - Change from having hammemrjs as dependency of this library to having it
as
peerDependency
. Thanks @mojoaxel.
- Add ESM support. Thanks @mojoaxel.
- Upgraded to
[email protected]
. Thanks @mojoaxel.
- Fixed #6: stopPropagation not binding to the original event.
- Made
propagating-hammerjs
more robust against removing/attaching a DOM element in the DOM whilst executing a touch event of the DOM element itself.
- Upgraded to Hammer.js v2.0.6.
- Replaced usage of
Hammer.extend
withHammer.assign
.
- Replaced usage of
- Fixed not working in case of multiple instances of propagating-hammerjs on the same DOM element. Thanks @jsdw.
- Fixed
dragend
events not being emitted correctly in case of multiple nested handlers.
- Fixed not being able to overload options when having overridden the global Hammer instance.
- Fixed not being able to handle both a tap and double tap.
- Extended the option
preventDefault
with values'mouse'
,'touch'
, and'pen'
to prevent default behavior for a specific type of device.
- Created an option
preventDefault
to enforce preventing the default browser behavior. - Fixed propagation not being handled correctly when the mouse pointer is being dragged outside the parent div.
- Fixed #2, the
emit
method not working.
- Removed using top level
this
, attachingpropagating
immediately towindow instead
.
- Added an event property
event.firstTarget
, always containing the element where a gesture started. - Fixed the
hammer.input
event blocking the emit of real events. - Fixed
panend
not being emitted whenpan
was used too.
- Fixed the module not working via commonjs.
- Added support for applying
propagating
to the Hammer constructor.
- Initial, fully functional release.