You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 8, 2021. It is now read-only.
Currently, touchend events (and possibly others) are stopped by code handling the "no tap on taphold" feature (#5983). This means that if one wants to detect touchend after a taphold then this is virtually impossible because the propagation is being stopped via event.stopPropagation(). The intent of this call (as described by commit #49bb033) is to prevent default action upon tap on an anchor element.
The text was updated successfully, but these errors were encountered:
(preventing vmouseup-s) if taphold is set to prevent a following tap event
This refines the modifications made in gh-5983.
(cherry picked from commit f95bec6)
Closesgh-6719Fixesgh-7494
Re gh-5983
Copying from #6719:
Currently, touchend events (and possibly others) are stopped by code handling the "no tap on taphold" feature (#5983). This means that if one wants to detect touchend after a taphold then this is virtually impossible because the propagation is being stopped via
event.stopPropagation()
. The intent of this call (as described by commit #49bb033) is to prevent default action upon tap on an anchor element.The text was updated successfully, but these errors were encountered: