Re: Errata for Touch Events: add a non-normative event sequence note

It might be worth adding that there can be zero or more touchmove events
before the touchend.  A common mistake is to assume that tap will never
contain a touchmove (see https://bugs.webkit.org/show_bug.cgi?id=138151 for
a recent discussion about the situation in Safari).

Otherwise LGTM.

On Wed, Oct 29, 2014 at 6:25 PM, Patrick H. Lauke <redux@splintered.co.uk>
wrote:

> As we did for PE, I believe it would be nice - from a "skim-reading"
> perspective,  to provide a clear listing of the event sequence a developer
> can expect as a result of a tap.
>
> I'd propose adding the following at the end of section 7, matching what we
> did in PE:
>
> <section class="note">
> <p>The activation of an element (a tap) would typically produce the
> following event sequence:</p>
> <ol data-class="note-list">
>         <li><code>touchstart</code></li>
>         <li><code>touchend</code></li>
>         <li><code>mousemove</code> <small>(for compatibility with legacy
> mouse-specific code)</small></li>
>         <li><code>mousedown</code></li>
>         <li><code>mouseup</code></li>
>         <li><code>click</code></li>
> </ol>
> <p>If, however, either the <code>touchstart</code> or
> <code>touchend</code> event has been cancelled during this interaction, no
> mouse or click events will be fired, and the resulting sequence of events
> would simply be:
> </p><ol data-class="note-list">
>         <li><code>touchstart</code></li>
>         <li><code>touchend</code></li>
> </ol>
> </section>
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
>