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

Sorry for the long delay in replying to this list Patrick, I've been
totally backlogged.   Catching up now.

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

> On 30/10/2014 01:33, Rick Byers wrote:
>
>> 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).
>>
>
> Agreed. I actually had that in initially, then thought I would end up
> opening a can of worms here with browsers that immediately fire a
> touchcancel after the slightest movement ;) ... but if you think it's cool
> to mention, yeah I'd prefer it in. So:
>
> [...]
>
>>              <li><code>touchstart</code></li>
>>
>
> <li>Zero or more <code>touchmove</code>events, depending on movement of
> the finger</li>
>
>               <li><code>touchend</code></li>
>>
> [...]
>
>>     <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>Zero or more <code>touchmove</code>events, depending on movement of
> the finger</li>
>
>               <li><code>touchend</code></li>
>>     </ol>
>>     </section>
>
>
LGTM


> Actually, would it still be useful to have some sentence (after the first
> sequence) to clarify that - depending on implementation - too much movement
> during the tap may result in the UA interpreting this as a gesture, rather
> than a tap, and therefore NOT firing compat events after touchend? If yes,
> I can wordsmith something...


This is really implementation specific (eg. I'm not sure IE's
implementation is as simple as 'too much movement during the tap', and even
Chrome's does has a timing element in addition to the movement).  I'm not
opposed to calling out the possibility non-normatively, but I don't think
it needs to be very explicit (obviously a "tap" isn't any touch sequence -
we're talking only about some specific UA-defined scenario here).


>
> 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
>