- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Thu, 30 Oct 2014 01:25:52 +0000
- To: public-touchevents@w3.org
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
Received on Thursday, 30 October 2014 01:26:18 UTC