- From: Andrei Popescu <andreip@google.com>
- Date: Mon, 4 Aug 2008 19:13:38 +0100
- To: "Aaron Boodman" <aa@google.com>
- Cc: "Chris Butler" <cbutler@dash.net>, "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 Mon, Aug 4, 2008 at 7:10 PM, Aaron Boodman <aa@google.com> wrote: > > 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? You can't clear a getCurrentPosition(). That callback could still fire after the timeout. Andrei
Received on Monday, 4 August 2008 18:14:29 UTC