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

Re: skeleton Geolocation API - Error codes

From: Aaron Boodman <aa@google.com>
Date: Mon, 4 Aug 2008 11:10:48 -0700
Message-ID: <278fd46c0808041110g7b39a2f8h7dcc84f67c0a57c9@mail.gmail.com>
To: "Chris Butler" <cbutler@dash.net>
Cc: "Andrei Popescu" <andreip@google.com>, "Shyam Habarakada" <shyamh@microsoft.com>, "Alec Berntson" <alecb@windows.microsoft.com>, "Doug Turner" <doug.turner@gmail.com>, "Chris Prince" <cprince@google.com>, public-geolocation@w3c.org 

On Wed, Jul 30, 2008 at 1:28 PM, Chris Butler <cbutler@dash.net> wrote:
> As you state you can use the setTimer to effectively do a timeout.  To
> avoid weird states you would need to be able to also store that you
> already timed out somewhere and check that every time that the callback
> is called.
>
> This would address the case that you show an error message to the user
> and then you get the callback.

Couldn't you just call clearWatch() after the timeout expires?

- a
Received on Monday, 4 August 2008 18:12:06 GMT

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