- From: Andrei Popescu <andreip@google.com>
- Date: Thu, 22 Apr 2010 10:53:06 +0100
- To: Olli@pettay.fi
- Cc: Steve Block <steveblock@google.com>, public-geolocation <public-geolocation@w3.org>, dougt@dougt.org
On Thu, Apr 22, 2010 at 10:41 AM, Olli Pettay <Olli.Pettay@helsinki.fi> wrote: > On 4/21/10 7:32 PM, Steve Block wrote: >> >>> "Implementations that are unable to provide all three angles must >>> set the values of the unknown angles to null" That is strange. The >>> type of the property is double. That kind of properties don't >>> usually give suddenly non-numeric values. >> >> There is precedent for this in the Geolocation spec. > > > Sounds like a bug in Geolocation draft, IMO > If the value isn't available, implementation could throw something > like NOT_AVAILABLE. > But then wouldn't you have to access all these properties from try / catch blocks? I don't think that's ideal and it's just more convenient to let them be null if they aren't available. Andrei
Received on Thursday, 22 April 2010 09:53:38 UTC