- From: <bugzilla@jessica.w3.org>
- Date: Mon, 04 Jun 2012 19:20:01 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17306 --- Comment #2 from Scott Graham <scott.w3bugzilla@h4ck3r.net> 2012-06-04 19:20:00 UTC --- (In reply to comment #1) > It should probably be the timestamp from when the connected event happened. > (When the gamepad was first exposed to script.) > > We should probably clarify what the values of .timestamp are. I think we have > two sane options: > 1) Equivalent to Date.now(), milliseconds since the epoch (limited time > resolution depending on platform). > 2) Equivalent to the High Resolution Time spec's DOMHighResTimeStamp values. > (fractional milliseconds since page load): > http://www.w3.org/TR/2012/WD-hr-time-20120313/#sec-DOMHighResTimeStamp Better > resolution + spec'ed to be monotonic. I think DOMHighResTimeStamp would be best to coordinate with audio, rAF, etc. I will update if there's no objection to that. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Monday, 4 June 2012 19:20:04 UTC