Re: Document effect of preventDefault on touchend event

Thanks Matt, this is great!  We had a similar bug in the old Android
browser, but it was fixed several years ago (perhaps the spec was written
so that the Android browser at the time would be compliant).  I agree we
should make these changes.  Want to edit the v1-errata draft, or shall I?

Thanks,
   Rick


On Thu, Jul 17, 2014 at 7:30 PM, Matt Brubeck <mbrubeck@mozilla.com> wrote:

>  After this Gecko bug is fixed, canceling a "touchend" event will prevent
> that touch from generating a click event and associated mouse events:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1016481
>
> The new Gecko behavior matches the current behavior of Chrome and WebKit.
>
> The Touch Events v1 recommendation does not explicitly document this
> behavior, though it is perhaps implied by the table in section 5.4.  To
> make it fully explicit, I suggest adding this text to section 5.6 ("The
> touchend event") in the errata:
>
> "*If this event is cancelled, any sequence of touch events that includes
> this event must not be interpreted as a click [link to section 7].*"
>
> and the following text (inserted text in bold below) to section 7:
>
> "If the preventDefault method of touchstart or touchmove* or touchend* is
> called, the user agent should not dispatch any mouse event that would be a
> consequential result of the the prevented touch event."
>