- From: <bugzilla@jessica.w3.org>
- Date: Mon, 17 Dec 2012 20:22:13 +0000
- To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20411 --- Comment #10 from Chris Wilson <cwilso@gmail.com> --- (In reply to comment #9) > Well, that kinda needs to happen regardless as it's part of the DOMEvent > interface. I guess what we need to say in the spec is that it reflects the > receivedTime to the nearest millisecond (rounded or floored?). Well that's the annoying part - since it's a completely different timeframe, it's a long conversion. At least it's not on another hardware clock, like audio. I'd suggest floored, but I think it's mostly irrelevant - I'd rather advise against using timeStamp, due to precision. I wish it weren't there. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 17 December 2012 20:22:16 UTC