Open tmtron opened 2 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
not stale
I don't see tap
firing with double == false
, but I realized that doubletap
events don't have a double
property. I'm going to add a double == true
property to doubletap
events.
If you want to ignore taps after hold, you can check tapEvent.dt < 500
If you want to ignore taps after hold, you can check tapEvent.dt < 500
thanks, that works: tapEvent.dt >= 500
can be detected to use a tap after hold (which I want to ignore)
I don't see tap firing with double == false
click target
tap
event fires (with double=false) first, and then the doubletap
event firesdouble
should be true
, for the tap
event , right?
When we double click, then
tap
will also fire (withevent.double
is false).The same is true for 'hold'
If I understood this comment https://github.com/taye/interact.js/issues/155#issuecomment-71202352 correctly, then it is expected, that (on double clikc) the
tap
event is also fired withevent.double=false
- but this is not the case (event.double=true
)Here is a full stackblitz example
Expected behavior
On double-click the tap event should fire and have
event.double=true
.On hold the tap event should not fire.
Actual behavior
On double-click the tap event fires and has
event.double=false
.On hold the 'hold' event fires, and then the tap event fires.
System configuration
1.10.11: Google Chrome Version 100.0.4896.88: Windows 10: