This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10609 - DOMTimeStamp should be defined in Web IDL
Summary: DOMTimeStamp should be defined in Web IDL
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: WebIDL (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Cameron McCormack
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-12 13:00 UTC by Anne
Modified: 2010-10-28 04:44 UTC (History)
2 users (show)

See Also:

Attachments

Description Anne 2010-09-12 13:00:03 UTC 
Since DOMString is also in Web IDL, DOMTimeStamp should move there too. (Maybe with advice that people should use date instead?)
Comment 1 Anne 2010-09-12 14:12:51 UTC 
Tentatively removed from Web DOM Core.
Comment 2 Cameron McCormack 2010-10-19 03:40:53 UTC 
I'm thinking DOMTimeStamp should just be a typedef to unsigned long long (or a uint53_t if such a type were introduced) with no special binding in JS (it would just be a Number).  You would need dates that exceed the year 200,000 before the precision of Number is an issue.

A separate Date type (name tbd) could be introduced for things like HTMLTimeElement.valueAsDate.
Comment 3 Anne 2010-10-19 07:48:10 UTC 
That works for me. I was going to suggest naming it just "timestamp" but since we "cannot" rename DOMString we might as well keep it as DOMTimeStamp.
Comment 4 Cameron McCormack 2010-10-28 04:44:40 UTC 
Added DOMTimeStamp to a new "Common definitions" section of Web IDL:

  http://dev.w3.org/2006/webapi/WebIDL/#common-DOMTimeStamp