ISSUE-3: Click events should be dispatched after any touch events are processed.
authorMatt Brubeck <mbrubeck@mozilla.com>
Tue, 19 Jul 2011 08:55:40 -0700
changeset 97 3f54db94ae0d
parent 96 457c2df41b66
child 98 4ad645b57624
ISSUE-3: Click events should be dispatched after any touch events are processed.
touchevents.html
--- a/touchevents.html	Fri Jun 10 10:42:28 2011 -0700
+++ b/touchevents.html	Tue Jul 19 08:55:40 2011 -0700
@@ -23,7 +23,7 @@
           // subtitle   :  "an excellent document",
 
           // if you wish the publication date to be other than today, set this
-          publishDate:  "2011-05-05",
+          publishDate:  "2011-07-19",
 
           // if the specification's copyright date is a range of years, specify
           // the start date here:
@@ -51,7 +51,7 @@
                 company: "W3C", companyURL: "http://w3.org/" },
               { name: "Sangwhan Moon",
                 company: "Opera Software ASA", companyURL: "http://www.opera.com/" },
-              { name: "Matt Brubeck",
+              { name: "Matt Brubeck", url: "http://limpet.net/mbrubeck/",
                 company: "Mozilla", companyURL: "http://www.mozilla.org/" },
           ],
 
@@ -548,6 +548,15 @@
       </p>
 
       <p>
+        If the user agent dispatches a <a>click</a> event in response to touch
+        input, the <a>click</a> event should be dispatched after the
+        <a>touchstart</a> and <a>touchend</a> events for the corresponding
+        touch point.  If the contents of the document change during processing
+        of the touch events, then the user agent may dispatch the <a>click</a>
+        event to a different target than the touch events.
+      </p>
+
+      <p>
         The default actions and ordering of any further touch and mouse events
         are implementation-defined, except as specified elsewhere.
       </p>