Clarify effect of canceling touchend event. · w3c/touch-events@54a3d16 (original) (raw)

This repository was archived by the owner on Jul 9, 2024. It is now read-only.

File tree

1 file changed

lines changed

1 file changed

lines changed

Original file line number Diff line number Diff line change
@@ -598,6 +598,12 @@

The touchend event

598 598 must not be included in the <a>touches</a> and <a>targetTouches</a>
599 599 attributes.
600 600 </p>
601 +
602 +<p>
603 + If this event is cancelled, any sequence of touch events that
604 + includes this event must not be <a href="#click-events">interpreted
605 + as a click</a>.
606 +</p>
601 607 </section>
602 608
603 609 <section>
@@ -715,9 +721,10 @@

Interaction with Mouse Events

715 721 user agent dispatches both touch events and mouse events in response to
716 722 a single user action, then the <a>touchstart</a> event type must be
717 723 dispatched before any mouse event types for that action. If the
718 -<a>preventDefault</a> method of <a>touchstart</a> or <a>touchmove</a>
719 - is called, the user agent should not dispatch any mouse event that
720 - would be a consequential result of the the prevented touch event.
724 +<a>preventDefault</a> method of <a>touchstart</a>, <a>touchmove</a>, or
725 +<a>touchend</a> is called, the user agent should not dispatch any mouse
726 + event that would be a consequential result of the the prevented touch
727 + event.
721 728 </p>
722 729
723 730 <p class="note">
@@ -727,7 +734,7 @@

Interaction with Mouse Events

727 734 touch input devices, it can react to the subsequent mouse events instead.
728 735 </p>
729 736
730 -<p>
737 +<p id="click-events">
731 738 If the user agent intreprets a sequence of touch events as a click,
732 739 then it should dispatch <a>mousemove</a>, <a>mousedown</a>,
733 740 <a>mouseup</a>, and <a>click</a> events (in that order) at the location