W3C home > Mailing lists > Public > public-geolocation@w3.org > August 2008

Re: skeleton Geolocation API - Error codes

From: Doug Turner <doug.turner@gmail.com>
Date: Mon, 11 Aug 2008 14:09:34 -0700
Cc: "Chris Butler" <cbutler@dash.net>, public-geolocation@w3c.org, "Shyam Habarakada" <shyamh@microsoft.com>, "Alec Berntson" <alecb@windows.microsoft.com>, "Chris Prince" <cprince@google.com>, "Aaron Boodman" <aa@google.com>, Aza <aza@mozilla.com>
Message-Id: <D2F86A2A-2C25-4BB4-B1FF-DCE052EE0CD4@gmail.com>
To: "Andrei Popescu" <andreip@google.com> 


On Aug 11, 2008, at 1:51 PM, Andrei Popescu wrote:

> Hi Chris,
>
> On Mon, Aug 11, 2008 at 2:44 PM, Chris Butler <cbutler@dash.net>  
> wrote:
>> Hi Andrei.
>>
>> I think there was consensus that we should have timeouts as part of  
>> the
>> API as an error scenario with the ability to set the timeout period.
>>
>> Was there something I missed that was a strong argument against?
>>
>
> I wasn't sure there was consensus, since there was the argument that
> you could achieve the same functionality using window.setTimeout().
> However, I do agree with you that allowing the developer to specify a
> timeout via PositionOptions is a nice-to-have feature. Does anyone
> strongly disagree with adding this to the spec?
>
> Andrei


You can not support this functionality with window.setTimeout() unless  
getCurrentPosition returns something that is cancelable.  I think this  
is a good addition.  We can support this via  a new error code on  
PositionError.

Regards,
Doug
Received on Monday, 11 August 2008 21:10:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 August 2009 20:54:07 GMT