- From: Max Froumentin <maxfro@opera.com>
- Date: Wed, 06 Jan 2010 11:22:55 +0100
- To: Anne van Kesteren <annevk@opera.com>
- CC: Thomas Roessler <tlr@w3.org>, "public-device-apis@w3.org" <public-device-apis@w3.org>
On 05/01/2010 18:09, Anne van Kesteren wrote: > On Tue, 05 Jan 2010 18:03:03 +0100, Max Froumentin <maxfro@opera.com> > wrote: >> On 05/01/2010 17:21, Thomas Roessler wrote: >>> - Milliseconds are an awkward unit to use for an estimate that's at >>> best accurate on a +- 10min scale. >> >> Yes, but it's still a time measurement value, and I think that it >> should be in the same unit as other similar values, starting with Date. > > <video> uses floats in seconds for attributes that take a time. Then I'm changing timeRemaining to seconds. But for the timeOut options, geolocation uses milliseconds so I'm keeping milliseconds too. Shout if that's not acceptable. Max.
Received on Wednesday, 6 January 2010 10:23:27 UTC