- From: Steve Block <steveblock@google.com>
- Date: Tue, 26 Jan 2010 17:02:26 +0000
- To: Tim McCarthy <timmccar@me.com>
- Cc: Richard Barnes <rbarnes@bbn.com>, Max Froumentin <maxfro@opera.com>, public-geolocation@w3.org
> Careful with that. Heading with no velocity is not actually null. It's > known but highly uncertain. If the user really is stationary, then I think the heading is undefined. > True, but returning null prevents the user from testing if your device supports heading, because in order to > do so you would have to check whether heading is null but only if your device is moving. > > There's no real reason not to set this to 0. As well. Or 24, 38, or anything. If there is no speed, it doesn't > matter. Being able to test that a device supports the parameter is valuable. I think that using any number when the heading is undefined is misleading. If we want to always be able to check if the heading is supported, we could use NaN when it's undefined, and null if unsupported. Steve -- Google UK Limited Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W 9TQ Registered in England Number: 3977902
Received on Tuesday, 26 January 2010 17:02:57 UTC