Remove the "timestamp" attribute from the TouchPoint interface.
authorMatt Brubeck <>
Tue, 12 Apr 2011 16:50:10 -0700
changeset 38 a5d5d9e55a66
parent 37 d5eb1e9315e7
child 39 a9346e501dcf
Remove the "timestamp" attribute from the TouchPoint interface.

The timeStamp attribute of the Event interface should be used instead.
This was discussed at:
--- a/touchevents.html	Tue Apr 12 11:05:32 2011 -0700
+++ b/touchevents.html	Tue Apr 12 16:50:10 2011 -0700
@@ -126,13 +126,6 @@
           the original proximal event target for this <a>touch point</a>.  The target must be an <a>Element</a>.
-        <dt>readonly attribute DOMTimeStamp timestamp</dt>
-        <dd>
-          The <a>timestamp</a> attribute represents the time when the <a>TouchPoint</a> was initiated and is represented as a DOMTimeStamp [[!DOM-LEVEL-3-CORE]].
-          <p class="issue" id="issue-timestamp-format"><strong>Issue:</strong> should we align to timestamp as defined in the <a href="">Geolocation API spec</a> (as above), or with the datetime as defined in the <a href="">HTML5 spec</a> (attribute DOMString dateTime, where datetime is a <a href="">valid global date and time string</a>), or to something else (see <a href="">this thread on Event.timeStamp</a>)?</p>
-          <p class="issue" id="issue-timestamp"><strong>Issue:</strong> Should each touchpoint have its own timestamp?  Or should we leave timestamps up to script authors?  My feeling is that having implicit timestamps may be useful in defining an author-defined gesture-like mapping between low-level and high-level events (e.g. a swipe vs. drag speed threshold expressed as the difference in timestamps)</p>
-        </dd>
         <dt>readonly attribute long screenX</dt>