[Bug 20220] New: hwTimestamp should be interoperable with the high resolution time spec

https://www.w3.org/Bugs/Public/show_bug.cgi?id=20220

            Bug ID: 20220
           Summary: hwTimestamp should be interoperable with the high
                    resolution time spec
    Classification: Unclassified
           Product: PointerEventsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Pointer Events specification
          Assignee: jrossi@microsoft.com
          Reporter: rbyers@chromium.org
        QA Contact: dave.null@w3.org
                CC: public-pointer-events-bugzilla@w3.org

PointerEvent has a hwTimestamp field, currently defined as:

A timestamp, in microseconds, of the pointer event as reported by hardware. The
origin time (e.g. hwTimestamp equals 0) is hardware and/or operating system
dependent. If the hardware does not provide a high resolution timestamp, then
the value must be 0.

However, for this value to be really useful it must be comparable to the
high-resolution time returned by other APIs.  In particular, the High
Resolution Time spec
(http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/HighResolutionTime/Overview.html)
defines specific semantics for such a value.  Can we just match those?

In fact, it sounds like 'systemTime' is going to be added to the DOM Event type
for this purpose
(http://lists.w3.org/Archives/Public/www-dom/2012OctDec/0022.html,
http://lists.w3.org/Archives/Public/public-web-perf/2012Oct/0046.html). 
Perhaps we should just remove hwTimestamp from pointer events, and rely on the
pending addition for all types of Event.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Monday, 3 December 2012 22:32:30 UTC