ISSUE-171: Consider removing Event.timeStamp value 0


Consider removing Event.timeStamp value 0

HISTORICAL: DOM3 Events [All Bugs and Issues use Bugzilla:]
Raised by:
Doug Schepers
Opened on:
Cameron McCormack <>:

The definition of Event.timeStamp is currently:

Used to specify the time at which the event was created in
milliseconds relative to 1970-01-01T00:00:00Z. Due to the fact that
some systems may not provide this information the value of timeStamp
may be not available for all events. When not available, the value
shall be 0.

I think we should remove the allowance for implementations to have
Event.timeStamp be 0. It might be that implementations are running on
systems that don’t know what the actual time is, but surely JS Date is
returning something; I think it would be fine for those implementations
to assume a particular time on startup, for example.

I don’t think we need to worry about implementations that can’t even
track the progress of time.

I also think we should make Event.timeStamp be not the time at which the
event was created (the construction of the Event object?) but the time
at which the event represented by the Event object occurred. For user
created events, we could have it be either the time that createEvent()
is called or the time that initEvent() is called (since timeStamp is
read only).
Related Actions Items:
No related actions
Related emails:
  1. ISSUE-171 and ISSUE-172 (from on 2011-07-29)
  2. Re: publish a new Working Draft of DOM Core; comment deadline March 2 (from on 2011-02-25)
  3. Minutes: DOM3 Events Telcon, 27 October 2010 (from on 2010-10-29)
  4. ISSUE-171 (Event.timeStamp): Consider removing Event.timeStamp value 0 [DOM3 Events] (from on 2010-10-20)

Related notes:

RESOLVED: 1) we keep timestamp as ms since epoch (for now); 2) we remove the allowance for implementations to give 0 when they can't determine it; and 3) it remains that the timeStamp is generated when the event object is created, not when the event is dispatched.

Doug Schepers, 25 Feb 2011, 00:17:05

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 171.html,v 1.1 2016/01/25 10:26:17 carine Exp $